/marchesml/awards/search

POST /api/marchesml/awards/search

Price: 45 credits

Search the weekly results of judged calls for tenders published by the Malian DGMP-DSP (Résultats des appels d'offres jugés) by subject words, contracting authority, winning company and results week. Each row is one evaluated procurement with its buyer, subject, bidders, funding source, evaluation date and, per lot, the winner, the amount in CFA francs and the execution period, plus the week of the bulletin. Newest week first.

How to use it

One call reads at most the 40 newest weekly bulletins inside the week window; set week_to to reach older weeks. lots holds what could be read per lot; award_text, amount_text and execution_period_text keep the bulletin's own wording, and text the whole entry, for the rows where a lot carries no amount. A lot marked is_unsuccessful was declared infructueux; a row marked is_unreadable is a bulletin whose text could not be read and carries only its week and link.

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 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 winning company name (examples: "SARL"; minLength: 1)
• week_from string nullable — Earliest results week end date (examples: "2026-01-01")
• week_to string nullable — Latest results week end date (examples: "2026-07-31")

Response

• @type string (default: "MarchesmlAward")
• name string nullable
• buyer_name string nullable
• funding string nullable
• evaluation_date string nullable
• evaluation_date_text string nullable
• bidder_count integer (default: 0)
• bidders array (default: [])
  • @type string (default: "MarchesmlAwardBidder")
  • name string required
  • lot string nullable
• lots array (default: [])
  • @type string (default: "MarchesmlAwardLot")
  • lot string nullable
  • winner_name string nullable
  • is_unsuccessful boolean (default: false)
  • amount number nullable
  • amount_max number nullable
  • currency string nullable
  • amount_text string nullable
  • execution_period string nullable
• award_text string nullable
• amount_text string nullable
• execution_period_text string nullable
• bulletin_title string nullable
• bulletin_url string required
• week_start_date string nullable
• week_end_date string nullable
• text string nullable
• is_unreadable boolean (default: false)

Errors

• 422 — 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.

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.