/marchescm/procurement-plans/search

POST /api/marchescm/procurement-plans/search

Price: 20 credits

Search the procurement plans of Cameroonian public buyers on the national e-procurement system (COLEPS) by budget year, project name words, project number, registration status, region and project owner, with the project, its lots, the nature of service, the project owner and the registration status.

How to use it

Each row is one planned project; id opens it with location, funding, procedure and lots through marchescm/procurement-plans, and equals project_number on the marchescm/tenders notices launched from it.

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: 15000)
• fiscal_year integer nullable — Budget year of the plan (examples: 2026; min: 2000; max: 2100)
• keyword string nullable — Words in the project name (examples: "forage"; minLength: 1)
• project_number string nullable — Project number (examples: "P20260800623"; pattern: ^P\d{11}$)
• registration_status string nullable — Registration status (one of: "new", "modified")
• region string nullable — Region of the project (one of: "ADAMAOUA", "CENTRE", "EST", "EXTREME-NORD", "LITTORAL", "NORD", "NORD-OUEST", "OUEST", "SUD", "SUD-OUEST")
• buyer_code string nullable — Code of the project owner (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)

Response

• @type string (default: "MarchescmPlanRow")
• id string required
• project_number string required
• modification_number string required
• examination_count integer nullable
• name string nullable
• task_name string nullable
• service_category string nullable
• owner_name string nullable
• registration_status string nullable
• lots array (default: [])
  • @type string (default: "MarchescmPlanRowLot")
  • lot_number integer nullable
  • name string nullable

Errors

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