POST /api/marchesml/procurement-plans/search
Price: 55 credits
Search the planned contracts in the current-year procurement plans (plans de passation des marchés) of Malian contracting authorities on the Mali public procurement portal by contract subject words, buyer, plan title and planned start date. Each row is one planned contract with its buyer and service, plan title and revision, contract type, procurement method, funding source, the planned date of each procurement step and the date each step was reached.
reference is the tender notice reference: the tender or expression of interest for the line carries the same value as its reference and the line id as planned_contract_id. contract_type is FRN supplies, TRV works, SC services or PRI intellectual services; procurement_method and funding are the portal's codes.
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)buyer string nullable — Part of the contracting authority name (examples: "MINISTERE DE LA SANTE"; minLength: 1)plan string nullable — Part of the plan title (examples: "plan de passation de l'exercice budgétaire 2026"; minLength: 1)start_from string nullable — Earliest planned start date (examples: "2026-01-01")start_to string nullable — Latest planned start date (examples: "2026-12-31")@type string (default: "MarchesmlPlannedContract")id string nullablename string nullablereference string nullablelinked_reference string nullableline_type string nullablecontract_type string nullableprocurement_method string nullablefunding string nullablebuyer_id string nullablebuyer_name string nullableservice_name string nullableplan_id string nullableplan_name string nullableplan_year integer nullableplan_revision integer nullableplan_published_at integer nullableplanned_start_date string nullableplanned_end_date string nullableplanned_dossier_submission_date integer nullableplanned_no_objection_date integer nullableplanned_publication_date integer nullableplanned_opening_date integer nullableplanned_evaluation_date integer nullableplanned_award_date integer nullabledossier_submitted_at integer nullableno_objection_at integer nullablepublished_at integer nullableopened_at integer nullableevaluated_at integer nullableawarded_at 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.