/marchesne/procurement-plans

POST /api/marchesne/procurement-plans

Price: 5 credits

One procurement plan from the Niger public procurement portal (marchespublics.ne) by id: plan reference, title, contracting authority, budget year, version, publication date and every planned contract with its reference, subject, contract type, procurement method, planned launch date and the buyer's department.

How to use it

Pass the id of a marchesne/procurement-plans/search row or the plan page URL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Procurement plan id or plan page URL (examples: "1158", "https://www.marchespublics.ne/marches-publics/1158"; minLength: 1)

Response

• @type string (default: "MarchesnePlan")
• id string required
• reference string required
• name string nullable
• buyer_name string nullable
• year integer nullable
• version integer nullable
• published_date string nullable
• planned_contract_count integer (default: 0)
• planned_contracts array (default: [])
  • @type string (default: "MarchesnePlannedContract")
  • reference string nullable
  • name string nullable
  • contract_type string nullable (one of: "goods", "works", "services", "consulting")
  • contract_type_label string nullable
  • procurement_method string nullable
  • launch_date string nullable
  • unit_name string nullable
  • revision_status string nullable
• url string required

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 — No procurement plan under that id 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.