/comprasal/tenders/search

POST /api/comprasal/tenders/search

Price: 20 credits

List the purchasing processes currently open on COMPRASAL, El Salvador's public procurement portal, optionally narrowed by keywords, buyer institution or contracting method. Each process carries its code, buyer, method, current stage, full stage calendar and goods and services categories.

How to use it

Covers the open opportunities register only; awarded processes are in comprasal/awards/search. Several keywords may be sent at once, and comprasal/tenders takes a process `id` for its detail.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keywords array nullable — Keywords matched against the process (examples: ["equipo"], ["medicamentos","insumos"])
• institution_id string nullable — COMPRASAL institution id of the buyer (examples: "14", "98")
• method string nullable — Contracting method code (one of: "LC", "CP", "CD", "SCSBCC", "SCSBCL", "SCSBPF", "SCSBCDC", "CL", "SCSFU", "SCSCI", "SCSMC", "COV", "SI", "SPP", "PUP", "ASE", "CatEl")
• offset integer — Number of processes to skip (default: 0; min: 0)
• count integer required — Max number of processes to return (min: 1; max: 500)

Response

• @type string (default: "ComprasalTender")
• id string required
• code string nullable
• internal_code string nullable
• version integer nullable
• buyer object nullable
  • @type string (default: "ComprasalInstitution")
  • id string nullable
  • code string nullable
  • name string required
• status string nullable
• state_id string nullable
• state string nullable
• method_id string nullable
• method string nullable
• method_code string nullable
• process_type_id string nullable
• is_public boolean nullable
• start_date string nullable
• contracting_date string nullable
• award_date string nullable
• awarded_amount number nullable
• currency string (default: "USD")
• created_at integer nullable
• published_at integer nullable
• current_stage object nullable
  • @type string (default: "ComprasalStage")
  • id string nullable
  • name string nullable
  • start_at integer nullable
  • end_at integer nullable
• stages array (default: [])
  • @type string (default: "ComprasalStage")
  • id string nullable
  • name string nullable
  • start_at integer nullable
  • end_at integer nullable
• activities array (default: [])
  • @type string (default: "ComprasalActivity")
  • id string nullable
  • code string nullable
  • name string required
  • kind_id string nullable
  • kind string nullable
• country string (default: "SV")

Errors

• 422 — The request body did not validate 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 — The entity was not found, or a precondition failed 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.