POST /api/marchesmg/procurement-plans/search
Price: 20 credits
Search the planned contracts in the procurement plans (PPM) of Malagasy contracting authorities on the ARMP Madagascar public procurement portal for one buyer and one year, narrowed by contract type, procurement method and subject words. Each row carries the buyer, contract type, subject, initial and revised estimated amounts, procurement method, funding source, beneficiary service and budget account, and the planned launch, bid opening and award dates.
buyer_id comes from marchesmg/buyers/search. revised_estimated_amount is empty where the plan shows no revised amount.
access-token string requiredtimeout 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 required — 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")@type string (default: "MarchesmgPlannedContract")name string nullablebuyer_name string nullablecontract_type string nullableprocurement_method string nullableestimated_amount number nullablerevised_estimated_amount number nullablefunding string nullablebeneficiary_service string nullablebudget_account string nullablebeneficiary_revised_estimated_amount number nullableplanned_launch_date string nullableplanned_bid_opening_date string nullableplanned_award_date string nullableyear integer nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.