/marchescm/tenders

POST /api/marchescm/tenders

Price: 5 credits

Get one Cameroonian call for tenders from the national e-procurement system (COLEPS) by its id, with the buyer and project owner, project, procedure, funding source, submission deadline, bid opening place, tender document fee, tender board, lots with their budget, estimated cost and bid bond, and the tender document download links.

How to use it

Pass the id of a marchescm/tenders/search row. project_number opens the procurement plan behind the notice through marchescm/procurement-plans.

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 marchescm/tenders/search (examples: "20260900571-00"; pattern: ^\d{11}-\d{2}$)

Response

• @type string (default: "MarchescmTender")
• id string required
• notice_number string required
• modification_number string required
• latest_modification_number string nullable
• is_test boolean nullable
• consultation_mode string nullable
• notice_status string nullable
• addendum_description string nullable
• project_number string nullable
• project_name string nullable
• buyer_name string nullable
• project_owner_name string nullable
• service_category string nullable
• procedure_type string nullable
• funding_source string nullable
• is_joint_bidding_allowed boolean nullable
• submission_deadline_at integer nullable
• bid_opening_place string nullable
• document_acquisition_place string nullable
• max_lots_per_bidder integer nullable
• execution_period string nullable
• document_fee number nullable
• currency string nullable
• tender_board string nullable
• approval_number string nullable
• attachment_name string nullable
• previous_modification_ids array (default: [])
• lots array (default: [])
  • @type string (default: "MarchescmLot")
  • lot_number integer nullable
  • name string nullable
  • details string nullable
  • quantity string nullable
  • unit string nullable
  • delivery_period string nullable
  • delivery_place string nullable
  • budget_amount number nullable
  • estimated_cost number nullable
  • bid_bond_amount number nullable
  • currency string nullable
• documents array (default: [])
  • @type string (default: "MarchescmDocument")
  • number string nullable
  • url 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 tender notice with this id on the Cameroon 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.