/marchestg/tenders/search

POST /api/marchestg/tenders/search

Price: 20 credits

Search tender dossiers published by Togolese contracting authorities on the national public procurement platform by subject, reference, procurement method, buyer, publication date and status, with the buyer, sector, submission deadline and bid opening time. Most recently entered first.

How to use it

Active tenders are those whose submission deadline is today or later; closed tenders are those the buyer closed after bid opening. Pass a row's id to marchestg/tenders for the dossier document and its opening and closing flags.

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: 5000)
• keyword string nullable — Words in the tender subject (examples: "route"; minLength: 1)
• reference string nullable — Part of the tender reference (examples: "AOI"; minLength: 1)
• procurement_method string nullable — Procurement method (one of: "international_tender", "national_tender", "open_tender", "price_inquiry", "consulting_services", "services", "expression_of_interest", "invoice")
• status string — Tender status (default: "all"; one of: "all", "active", "closed")

Response

• @type string (default: "MarchestgTender")
• id string required
• url string required
• reference string nullable
• subject string nullable
• buyer object nullable
  • @type string (default: "MarchestgBuyer")
  • id string required
  • name string nullable
  • image string nullable
• procurement_method object nullable
  • @type string (default: "MarchestgProcurementMethod")
  • id string nullable
  • code string nullable
  • name string nullable
  • visibility string nullable
• sector object nullable
  • @type string (default: "MarchestgCode")
  • id string nullable
  • code string nullable
  • name string nullable
• published_date string nullable
• submission_deadline_at integer nullable
• bid_opening_at integer nullable
• closed_at integer nullable
• has_bids_opened boolean nullable
• is_closed boolean 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.