/marchestg/procurement-plans/search

POST /api/marchestg/procurement-plans/search

Price: 10 credits

Search procurement plans published by Togolese contracting authorities on the national public procurement platform by title, buyer, plan year and publication date, with the plan document. Latest publication first.

How to use it

Each row is one published plan or plan revision of one buyer, with its document. year is empty on plans published without one, and the year filter leaves those out. A plan whose document cannot be retrieved is served without it, and the X-Warning header states how many.

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 date (examples: "2026-01-01")
• date_to string nullable — Latest date (examples: "2026-06-30")
• buyer_id string nullable — Contracting authority id from marchestg/buyers/search (examples: "105")
• count integer required — Max number of results (min: 1; max: 1000)
• keyword string nullable — Words in the plan title (examples: "revise"; minLength: 1)
• year integer nullable — Plan year (examples: 2025; min: 2000; max: 2100)

Response

• @type string (default: "MarchestgPlan")
• id string required
• year integer nullable
• published_date string nullable
• buyer object nullable
  • @type string (default: "MarchestgBuyer")
  • id string required
  • name string nullable
  • image string nullable
• created_at integer nullable
• updated_at integer nullable
• document_url string nullable
• document_type 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.