/marchesmg/contracts/search

POST /api/marchesmg/contracts/search

Price: 20 credits

Search the public contracts signed by Malagasy contracting authorities and published by the ARMP Madagascar public procurement portal for one year, by buyer, buyer category, region, contract type, procurement method, subject words and contract holder. Each row is one contract with its code, subject, buyer, type, procurement method, amount including tax and currency, the holders with their tax id and beneficial owners, and the procurement officer (PRMP).

How to use it

A contract signed with a joint venture lists each holder under suppliers; amount is empty when the holders carry different amounts, which stay on each supplier. buyer_id comes from marchesmg/buyers/search.

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)
• keyword string nullable — Words to find in the subject (examples: "construction"; minLength: 1)
• year integer required — Budget year (examples: 2026; min: 2015)
• buyer_id string nullable — Contracting authority id from marchesmg/buyers/search (examples: "9001")
• contract_type string nullable — Type of contract (one of: "supplies", "services", "consulting", "works")
• procurement_method string nullable — Procurement method (one of: "direct_purchase", "expression_of_interest", "open_tender", "international_open_tender", "prequalified_open_tender", "restricted_tender", "international_restricted_tender", "posted_consultation", "price_consultation", "single_source")
• buyer_category string nullable — Category of contracting authority (one of: "local_authority", "public_establishment", "institution", "ministry", "state_company")
• region string nullable — Region of the contracting authority (one of: "alaotra-mangoro", "ambatosoa", "amoroni-mania", "analamanga", "analanjirofo", "androy", "anosy", "atsimo-andrefana", "atsimo-atsinanana", "atsinanana", "betsiboka", "boeny", "bongolava", "centrale", "diana", "fitovinany", "haute-matsiatra", "ihorombe", "itasy", "melaky", "menabe", "sava", "sofia", "vakinankaratra", "vatovavy", "vatovavy-fitovinany")
• supplier string nullable — Part of the contract holder name, or its tax id (NIF) (examples: "SOCIETE"; minLength: 1)

Response

• @type string (default: "MarchesmgContract")
• contract_code string required
• name string nullable
• year integer nullable
• buyer_id string nullable
• buyer_name string nullable
• buyer_category string nullable
• contract_type string nullable
• procurement_method string nullable
• execution_modality string nullable
• amount number nullable
• currency string nullable
• supplier_count integer (default: 0)
• suppliers array (default: [])
  • @type string (default: "MarchesmgSupplier")
  • name string nullable
  • tax_id string nullable
  • amount number nullable
  • beneficial_owner_names array (default: [])
• procurement_officer_name 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.