/marchescm/tenders/search

POST /api/marchescm/tenders/search

Price: 20 credits

Search calls for tenders of Cameroonian public buyers on the national e-procurement system (COLEPS) by title words, notice number, nature of service, notice kind, procedure, real or test notice, buyer, publication date and bid opening date, with the buyer, procedure, notice status and the status of each lot. Newest notice number first.

How to use it

Each row is one notice; id opens it with lots, budgets, deadline and documents through marchescm/tenders. Without dates the whole archive is searched.

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; max: 8000)
• keyword string nullable — Words in the notice title (examples: "construction"; minLength: 1)
• notice_number string nullable — Notice number (examples: "20260900571"; pattern: ^\d{11}$)
• service_category string nullable — Nature of the service (one of: "AG", "AI", "BEC", "ROUTES", "SNQ-PI", "SQ")
• notice_type string nullable — Kind of notice (one of: "new", "addendum")
• procedure_type string nullable — Procurement procedure (one of: "AONO", "AOIO", "AONR", "AOIR", "DC", "GG", "AOC", "AO2E", "CI")
• is_test boolean nullable — Test notices only (true) or real notices only (false)
• buyer_code string nullable — Buyer code (examples: "9915050004"; pattern: ^\d{10}$)
• buyer_name string nullable — Buyer name or its beginning, any case: a full name selects that buyer, a beginning shared by up to 5 buyers covers them all (examples: "HOPITAL GENERAL DE GAROUA"; minLength: 1)
• published_from string nullable — Earliest publication date (format: date; examples: "2026-01-01")
• published_to string nullable — Latest publication date (format: date; examples: "2026-09-30")
• bid_opening_from string nullable — Earliest bid opening date (format: date; examples: "2026-10-01")
• bid_opening_to string nullable — Latest bid opening date (format: date; examples: "2026-12-31")

Response

• @type string (default: "MarchescmTenderRow")
• id string required
• notice_number string required
• modification_number string required
• buyer_name string nullable
• procedure_type string nullable
• service_category string nullable
• notice_status string nullable
• lots array (default: [])
  • @type string (default: "MarchescmLotStatus")
  • lot_number integer nullable
  • status string nullable

Errors

• 422 — A date range is inverted, both buyer filters were given, or more than 5 buyers start with buyer_name 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.