/dgcp/tenders/search

POST /api/dgcp/tenders/search

Price: 20 credits

List Dominican public procurement processes from the DGCP open data by purchasing unit, procedure, state, SME targeting and publication date range. Returns the process record with its title, estimated amount, dates and flags per row.

How to use it

There is no text search and no supplier or category filter: narrow by `buyer_id`, `status` and a publication date range, then read titles. Rows carry no supplier: take `ocid` into dgcp/tenders for contracts, bids and documents.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• buyer_id integer nullable — Purchasing unit code, as in dgcp/buyers (examples: 147; min: 1)
• procurement_method string nullable — Procurement procedure label as the portal prints it (examples: "Comparación de Precios", "Licitación Pública Nacional"; minLength: 1)
• status string nullable — State of the process (one of: "Proceso publicado", "Proceso con etapa cerrada", "Sobres abiertos o aperturados", "Proceso adjudicado y celebrado", "Proceso desierto", "Cancelado")
• sme_only boolean — Keep only processes directed at SMEs (default: false)
• women_sme_only boolean — Keep only processes directed at women-led SMEs (default: false)
• date_from string nullable — Earliest publication date (examples: "2026-09-15")
• date_to string nullable — Latest publication date (examples: "2026-09-16")
• process_code string nullable — Process code (examples: "DIE-CCC-LPN-2026-0003"; minLength: 1)
• count integer required — Max number of processes to return (min: 1; max: 2000)

Response

• @type string (default: "DgcpProcess")
• code string required
• ocid string required
• description string nullable
• status string nullable
• buyer_id string nullable
• buyer_name string nullable
• procurement_method string nullable
• exception_type string nullable
• category string nullable
• subcategory string nullable
• currency string nullable
• estimated_amount number nullable
• published_at integer nullable
• amendment_deadline_at integer nullable
• bid_deadline_at integer nullable
• bid_opening_at integer nullable
• second_bid_opening_at integer nullable
• bidder_qualification_at integer nullable
• estimated_award_at integer nullable
• contract_signing_at integer nullable
• sme_directed boolean nullable
• women_sme_directed boolean nullable
• has_lots boolean nullable
• is_snip boolean nullable
• snip_code string nullable
• notified_suppliers integer nullable
• requesting_area string nullable
• planned_acquisition boolean nullable
• unplanned_justification string nullable
• presidential_decree boolean nullable
• top_authority_resolution boolean nullable
• external_financing boolean nullable
• decree_3122 boolean nullable
• green_purchase boolean nullable
• joint_purchase boolean nullable
• contract_duration string nullable
• country string (default: "DO")
• url string nullable

Errors

• 422 — A date lacks its pair, or the process code is not in the DGCP form 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.