POST /api/marchesml/awards/search
Price: 60 credits
Search the public contracts awarded and numbered by Malian contracting authorities on the Mali public procurement portal by subject words, contracting authority, contract holder and numbering date. Each row is one contract with its number, subject, buyer and service, contract type, procurement method, funding source, numbering time and the contract holder with its tax id (NIF) and the amount in CFA francs. Newest first.
week_from and week_to bound the contract numbering date. lots holds one entry per contract with the holder and amount; contract_type is mostly FRN supplies, TRV works, SC services and PRI intellectual services, with a few rows carrying SCX, F or T.
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: "MINISTERE DE LA SANTE"; minLength: 1)winner string nullable — Part of the contract holder's name (examples: "SARL"; minLength: 1)week_from string nullable — Earliest contract numbering date (examples: "2026-01-01")week_to string nullable — Latest contract numbering date (examples: "2026-07-31")@type string (default: "MarchesmlAward")contract_number string nullablename string nullablebuyer_name string nullableservice_name string nullablecontract_type string nullableprocurement_method string nullablefunding string nullablenumbered_at integer nullablelots array (default: [])@type string (default: "MarchesmlAwardLot")winner_name string nullablewinner_nif string nullableis_unsuccessful boolean (default: false)amount number nullablecurrency 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.