/dncp/tenders/search

POST /api/dncp/tenders/search

Price: 20 credits

Search Paraguayan public procurement processes on the DNCP portal by title words, buyer, awarded supplier, procurement category, UNSPSC item codes, procedure, stage, institution type and a date range on publication, bid deadline, award or contract signature. Returns the process summary with buyer, stage, deadline and the awarded suppliers per row.

How to use it

At least one filter is required. Text filters match whole terms, so `query: "medicamento"` and `"medicamentos"` are different searches, and `buyer` needs the entity's name as printed, not an acronym. A `Planificada` process is a planning entry with no title yet, only the buyer and category. The summary has no amount: take `ocid` into dncp/tenders for the call value, items, awards and contracts. `suppliers` lists the award suppliers, mostly on awarded processes; `stage: "Adjudicada"` is the filter that lists them.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Words of the call title, matched as a phrase (examples: "medicamentos", "adquisicion medicamentos"; minLength: 1)
• buyer_id integer nullable — SICP code of the procuring entity, as in dncp/buyers (examples: 306; min: 1)
• buyer string nullable — Procuring entity name as the portal prints it (examples: "Ministerio de Salud"; minLength: 1)
• supplier_id string nullable — RUC of an awarded supplier (examples: "80025906-8"; minLength: 1)
• supplier string nullable — Awarded supplier name (examples: "policlinica"; minLength: 1)
• categories array — Main procurement categories, any of (default: []; one of: "goods", "services", "works")
• classification_ids array — UNSPSC level-4 codes of the items, any of (default: []; examples: ["51142106","51142001"])
• procurement_method string nullable — Procurement procedure label as the portal prints it (examples: "Licitación Pública Nacional", "Menor cuantía nacional"; minLength: 1)
• stage string nullable — Stage of the process (one of: "Planificada", "En Convocatoria (Abierta)", "En Evaluacion (Cerrada)", "Adjudicada", "Anulada o Cancelada", "Desierta", "Suspendida")
• institution_type string nullable — Kind of procuring institution as the portal prints it (examples: "Entidades Descentralizadas", "Organismos de la Administración Central"; minLength: 1)
• date_from string nullable — Start of the date range (examples: "2026-09-01")
• date_to string nullable — End of the date range (examples: "2026-09-21")
• date_type string — Which process date the range applies to (default: "publicacion_llamado"; one of: "publicacion_llamado", "entrega_ofertas", "adjudicacion", "firma_contrato", "fecha_release")
• sort string nullable — Order of the rows (one of: "released_desc", "released_asc", "deadline_desc", "deadline_asc")
• count integer required — Max number of processes to return (min: 1; max: 1000)

Response

• @type string (default: "DncpTenderSummary")
• ocid string required
• process_id string nullable
• tender_id string nullable
• stage string nullable
• buyer object nullable
  • @type string (default: "DncpOrganization")
  • id string nullable
  • name string nullable
• procuring_entity object nullable
  • @type string (default: "DncpOrganization")
  • id string nullable
  • name string nullable
• suppliers array (default: [])
  • @type string (default: "DncpOrganization")
  • id string nullable
  • name string nullable
• deadline_at integer nullable
• released_at integer nullable
• country string (default: "PY")
• url string required
• record_url string required
• procurement_method_details string nullable
• main_category_details string nullable
• covered_by array (default: [])
• tender_period object nullable
  • @type string (default: "DncpPeriod")
  • start_at integer nullable
  • end_at integer nullable
  • max_extent_at integer nullable
  • duration_days integer nullable
• awards array (default: [])
  • @type string (default: "DncpAwardSummary")
  • id string required
  • suppliers array (default: [])
    • @type string (default: "DncpOrganization")
    • id string nullable
    • name string nullable
• contract_ids array (default: [])
• complaint_ids array (default: [])

Errors

• 422 — No filter was given, a date lacks its pair, or an id does not match its format 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.