/panamacompra/tenders/search

POST /api/panamacompra/tenders/search

Price: 20 credits

Search Panamanian public procurement processes on PanamaCompra by title words, process state, procedure type and the date of the current state. Returns the process number, title, state, entity and purchasing unit per row, newest state change first.

How to use it

Rows start in 2023. Take a row `id` into panamacompra/tenders for the conditions, items, documents and, once awarded, the winning supplier with its offer.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Words in the process title (examples: "computadoras"; minLength: 2)
• status integer nullable — Process state (one of: 1011, 1013, 4, 16, 44, 37, 1012, 19, 36)
• procedure_type integer nullable — Procedure type (one of: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 15, 16, 17, 19)
• date_from string nullable — Earliest date of the current state (format: date; examples: "2026-08-01")
• date_to string nullable — Latest date of the current state (format: date; examples: "2026-09-22")
• count integer required — Max number of processes to return (min: 1; max: 1000)

Response

• @type string (default: "PanamacompraTenderRow")
• id string required
• process_number string nullable
• process_id string nullable
• flow_id string required
• procedure_type_id string required
• procedure_type string nullable
• prefix string nullable
• status string nullable
• stage string nullable
• award_modality string nullable
• contract_object string nullable
• buyer object nullable
  • @type string (default: "PanamacompraBuyerRef")
  • name string nullable
  • dependency string nullable
  • purchasing_unit string nullable
  • province string nullable
  • address string nullable
• notes string nullable
• status_changed_at integer nullable
• country string (default: "PA")

Errors

• 422 — date_from is after date_to 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.