/seace/tenders/search

POST /api/seace/tenders/search

Price: 20 credits

Search Peruvian public procurement processes published on SEACE by words, procuring entity, year and month, procurement category, procedure, SEACE system version and stage reached. Each row carries the ocid, title, buyer, category, procedure, estimated value, tender period, and the ids of its awards and contracts.

How to use it

Without `query` the newest processes come first; with `query` the rows are not in date order. `procurement_method` must match the label exactly, and older records spell it in capitals (`LICITACION PUBLICA`), so the same procedure may need two searches. Pass a row's `id` to seace/tenders for items, documents, awards, contracts and parties.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of processes to return (min: 1; max: 1000)
• offset integer — How many processes to skip before the first returned one (default: 0; min: 0; <: 10000)
• query string nullable — Words in the process record (examples: "medicamentos"; minLength: 2)
• buyer_id string nullable — SEACE code of the procuring entity (examples: "PE-CONSUCODE-2543", "2543")
• year integer nullable — Year of the process (examples: 2025; min: 2000; max: 2100)
• month integer nullable — Month of the process within year (examples: 3; min: 1; max: 12)
• category string nullable — Main procurement category (one of: "goods", "works", "services")
• procurement_method string nullable — Procurement procedure label as SEACE prints it (examples: "Licitación Pública", "Adjudicación Simplificada"; minLength: 2)
• system string nullable — SEACE system version that published the process (one of: "seace_v3", "seace_v2")
• stage string nullable — Only processes that reached this stage (one of: "planning", "award", "contract")

Response

• @type string (default: "SeaceTenderSummary")
• id string required
• tender_id string nullable
• official_number string nullable
• description string nullable
• stage string nullable
• system string nullable
• buyer object nullable
  • @type string (default: "SeaceOrganizationRef")
  • id string required
  • name string nullable
• procuring_entity object nullable
  • @type string (default: "SeaceOrganizationRef")
  • id string required
  • name string nullable
• category string nullable
• additional_categories array (default: [])
• procurement_method string nullable
• procurement_method_details string nullable
• value object nullable
  • @type string (default: "SeaceValue")
  • amount number required
  • currency string nullable
  • amount_pen number nullable
  • exchange_rate number nullable
• has_protected_information boolean nullable
• tenderer_count integer nullable
• tender_period object nullable
  • @type string (default: "SeacePeriod")
  • start_at integer nullable
  • end_at integer nullable
  • duration_days integer nullable
• deadline_at integer nullable
• released_at integer nullable
• award_ids array (default: [])
• contract_ids array (default: [])
• country string (default: "PE")
• url string required

Errors

• 422 — A malformed buyer code, month without year, or a value outside its range 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.