/marchesga/procurement-plans/search

POST /api/marchesga/procurement-plans/search

Price: 10 credits

Search procurement plans (PPM) published on the Gabonese public procurement portal (DGMP) by budget mission name and publication date, with the plan number, mission, ministry, contracting authority, plan type, programme code and name, operator, programme manager, validation date and a link to the plan document. Newest publication first.

How to use it

Each row is one plan of a budget programme or operator; plan_document is the published plan itself.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• date_from string nullable — Earliest publication date (examples: "2026-01-01")
• date_to string nullable — Latest publication date (examples: "2026-06-30")
• offset integer — How many matches to skip before the first returned row (default: 0; min: 0)
• count integer required — Max number of results (min: 1; max: 100)
• keyword string nullable — Words in the budget mission name (examples: "JUSTICE", "SANTE"; minLength: 1)

Response

• @type string (default: "MarchesgaProcurementPlan")
• id string required
• url string nullable
• published_date string nullable
• updated_date string nullable
• reference string nullable
• mission string nullable
• administration_name string nullable
• buyer_name string nullable
• plan_type string nullable
• programme_code string nullable
• programme_name string nullable
• operator_name string nullable
• programme_manager_name string nullable
• validation_date string nullable
• plan_document object nullable
  • @type string (default: "MarchesgaDocument")
  • name 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 — 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.