/marchesbj/tenders

POST /api/marchesbj/tenders

Price: 1 credit

Get one Beninese call for tenders from the national public procurement portal by its id, with the reference, subject, contract type, buyer and its contact details, publication and award publication dates, lot count, submission deadline, bid opening time, where to obtain the tender documents and the notice document.

How to use it

Pass the id of a marchesbj/tenders/search row. The winner of an awarded tender is on the marchesbj/awards/search row whose tender_reference equals this reference.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tender_id string required — Tender id from marchesbj/tenders/search (examples: "1230944")

Response

• @type string (default: "MarchesbjTender")
• id string required
• reference string nullable
• subject string nullable
• contract_type object nullable
  • @type string (default: "MarchesbjCode")
  • id string nullable
  • code string nullable
  • name string nullable
• buyer object nullable
  • @type string (default: "MarchesbjBuyer")
  • id string required
  • name string nullable
  • abbreviation string nullable
  • buyer_type object nullable
    • @type string (default: "MarchesbjCode")
    • id string nullable
    • code string nullable
    • name string nullable
  • email string nullable
  • phone string nullable
  • fax string nullable
  • website_url string nullable
  • manager_name string nullable
• created_date string nullable
• published_date string nullable
• provisional_award_published_date string nullable
• final_award_published_date string nullable
• submission_deadline_at integer nullable
• bid_opening_at integer nullable
• document_pickup_location string nullable
• is_divisible_into_lots boolean nullable
• lot_count integer nullable
• is_document_downloadable boolean nullable
• document_url string nullable
• document_name string nullable

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 — No record with this id on the Benin public procurement portal 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.