POST /api/marchesci/approved-contracts/search
Price: 20 credits
Search public contracts approved in Cote d'Ivoire, listed by the public procurement directorate (marchespublics.ci), by subject words, buyer, contract holder, contract number, procurement method, amount and approval date. Each row carries the contract number, contract holder, buyer, approval date, procurement method, amount in XOF tax included and subject. Latest approval first.
One contract number can carry several rows, one per lot or holder. procurement_method holds abbreviations such as PSL, PSO and POR beside spelled-out names, so match both forms.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)count integer required — Max number of results (min: 1)keyword string nullable — Words to find in the subject (examples: "construction"; minLength: 1)buyer string nullable — Part of the contracting authority name (examples: "CONSEIL REGIONAL"; minLength: 1)winner string nullable — Part of the contract holder name (examples: "SARL"; minLength: 1)contract_number string nullable — Part of the contract number (examples: "2023-0-11-00-1-0020"; minLength: 1)procurement_method string nullable — Part of the procurement method name (examples: "PSL"; minLength: 1)amount_min number nullable — Lowest amount in XOF, tax included (examples: 10000000; min: 0)amount_max number nullable — Highest amount in XOF, tax included (examples: 500000000; min: 0)approved_from string nullable — Earliest approval date (examples: "2025-01-01")approved_to string nullable — Latest approval date (examples: "2025-12-31")@type string (default: "MarchesciApprovedContract")contract_number string nullablewinner_name string nullablebuyer_name string nullableapproval_date string nullableprocurement_method string nullableamount number nullablecurrency string nullablename string nullable422 — The request body did not validate 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.