/marchesne/awards/search

POST /api/marchesne/awards/search

Price: 10 credits

Search final award notices of the Niger public procurement portal (marchespublics.ne) by subject words, buyer, winning company, contract type, business sector, community, national or international scope, approval date and publication date. Each row is one awarded lot: notice reference, subject, lot number and label, winning company, approval and publication dates, buyer, sector, procurement method and contract type.

How to use it

One notice awarding several lots yields one row per lot, so group rows on reference plus name to rebuild a notice. No award amount is published.

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)
• buyer string nullable — Part of the contracting authority name (examples: "MINISTERE DE LA SANTE"; minLength: 1)
• published_from string nullable — Earliest publication date (examples: "2026-01-01")
• published_to string nullable — Latest publication date (examples: "2026-06-30")
• winner string nullable — Part of the winning company name (examples: "CFAO MOTORS"; minLength: 1)
• contract_types array nullable — Types of contract (one of: "goods", "works", "services", "consulting"; examples: ["goods","works"])
• sectors array nullable — Business sectors (one of: "agricultural_inputs_and_equipment", "services", "sanitation", "pharmaceutical_and_laboratory_products", "livestock_purchase", "office_supplies", "miscellaneous_supplies", "fuel", "electricity", "medical_supplies", "consulting", "teaching_equipment", "laboratory_equipment", "it_consumables", "general_printing", "office_furniture", "hygiene_products", "refrigeration_and_appliances", "security_services", "repair_maintenance_and_installation", "current_supplies", "works", "insurance", "it_equipment", "food", "meat_purchase", "condiments_purchase", "foodstuffs_purchase", "vehicles"; examples: ["miscellaneous_supplies","medical_supplies"])
• notice_scopes array nullable — Community, national or international call (one of: "community", "national", "international"; examples: ["community"])
• approved_from string nullable — Earliest approval date (examples: "2024-01-01")
• approved_to string nullable — Latest approval date (examples: "2024-12-31")

Response

• @type string (default: "MarchesneAward")
• reference string nullable
• name string nullable
• lot_number integer nullable
• lot_name string nullable
• winner_name string nullable
• approval_date string nullable
• published_date string nullable
• buyer_name string nullable
• sector string nullable
• procurement_method string nullable
• contract_type string nullable (one of: "goods", "works", "services", "consulting")
• contract_type_label 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.