/marchessn/awards

POST /api/marchessn/awards

Price: 5 credits

Get one award notice from the Senegal national public procurement portal by its id or URL, with the subject, contracting authority, provisional or final notice title, tender reference, awarded amount, number of bids, winner, delivery period and the full notice text.

How to use it

Notices written as free text leave the numbered fields empty; notice_text then carries the winner and amount. tender_reference often equals reference on a marchessn/tenders/search row.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• award_id string required — Award notice id or the award notice URL (examples: "59100", "https://www.marchespublics.sn/index.php?option=com_attribution&task=view_texte&idavis=59100&Itemid=203")

Response

• @type string (default: "MarchessnAward")
• id string required
• subject string nullable
• buyer_name string nullable
• notice_title string nullable
• tender_reference string nullable
• publication_reference string nullable
• tender_published_date string nullable
• amount number nullable
• currency string nullable
• bids_received integer nullable
• awardee_name string nullable
• delivery_period string nullable
• notice_items array nullable
  • @type string (default: "MarchessnAwardItem")
  • number integer required
  • label string required
  • value string nullable
• notice_text string nullable
• url string required

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 Senegal public procurement portal publishes no notice page for this id 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.