POST /api/comprasal/tenders
Price: 1 credit
One El Salvador public purchasing process by process id, open or awarded: its codes, buyer, method, tracking status, start, contracting, publication and award dates, awarded amount in USD and the full stage calendar.
Takes a process `id` from comprasal/tenders/search or a `process_id` from comprasal/awards/search. `stages` lists every stage of the process with its start and end.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)id string required — Process id from comprasal/tenders/search, or process_id from comprasal/awards/search (examples: "139080", "135001"; minLength: 1)@type string (default: "ComprasalTender")id string requiredcode string nullableinternal_code string nullableversion integer nullablebuyer object nullable@type string (default: "ComprasalInstitution")id string nullablecode string nullablename string requiredstatus string nullablestate_id string nullablestate string nullablemethod_id string nullablemethod string nullablemethod_code string nullableprocess_type_id string nullableis_public boolean nullablestart_date string nullablecontracting_date string nullableaward_date string nullableawarded_amount number nullablecurrency string (default: "USD")created_at integer nullablepublished_at integer nullablecurrent_stage object nullable@type string (default: "ComprasalStage")id string nullablename string nullablestart_at integer nullableend_at integer nullablestages array (default: [])@type string (default: "ComprasalStage")id string nullablename string nullablestart_at integer nullableend_at integer nullableactivities array (default: [])@type string (default: "ComprasalActivity")id string nullablecode string nullablename string requiredkind_id string nullablekind string nullablecountry string (default: "SV")422 — The id is not a numeric process id Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No public COMPRASAL process under that id Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.