/mercadopublico/tenders/search

POST /api/mercadopublico/tenders/search

Price: 20 credits

Search Chilean public tenders on Mercado Público by words or tender code, state, region, tender type, required guarantee, budget publicity and publication dates. Returns the tender code, title, description, state, amount or amount band, publication and closing dates and the buying organisation per row.

How to use it

`value` is set when the tender publishes an amount; otherwise `amount_band` carries the UTM band. Take a row `id` into mercadopublico/tenders for dates, criteria, bids, awards and the winning suppliers.

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 or a tender code (examples: "computadores", "4116-5-LE26"; minLength: 3)
• status string nullable — Tender state (one of: "5", "6", "7", "8", "15", "16")
• region string nullable — Region the tender is issued in (one of: "1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12", "13", "14", "15", "16")
• tender_type string nullable — Tender type (one of: "1", "2", "3", "24", "25", "23", "30", "13", "9", "10", "26", "27", "29", "31", "32", "33", "34", "35")
• guarantee string nullable — Guarantee the tender requires (one of: "0", "1", "2", "3")
• public_budget boolean nullable — True keeps tenders that publish their budget, False those that do not
• published_from string nullable — Earliest publication date (format: date; examples: "2026-09-01")
• published_to string nullable — Latest publication date (format: date; examples: "2026-09-10")
• order string — Result order (default: "1"; one of: "1", "2", "3", "4", "5", "6", "7", "8")
• count integer required — Max number of tenders to return (min: 1; max: 500)

Response

• @type string (default: "MercadopublicoTenderRow")
• id string required
• ocid string required
• description string nullable
• status string nullable
• stage string nullable
• tender_type string nullable
• value object nullable
  • @type string (default: "MercadopublicoValue")
  • amount number nullable
  • currency string nullable
• value_kind string nullable
• amount_band string nullable
• published_date string nullable
• closing_date string nullable
• buyer object nullable
  • @type string (default: "MercadopublicoBuyerRef")
  • id string nullable
  • name string nullable
  • unit string nullable
• buyer_purchase_count integer nullable
• buyer_late_payment_claim_count integer nullable
• country string (default: "CL")
• url string required

Errors

• 422 — Only one of published_from and published_to was given, or they are reversed 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.