/worldbank/other-sanctions

POST /api/worldbank/other-sanctions

Price: 5 credits

List firms and individuals under other World Bank sanctions (reprimand or conditional non-debarment)

How to use it

List firms and individuals under World Bank Group sanctions other than debarment — i.e. those issued a letter of reprimand or placed under conditional non-debarment (Table 2 of the World Bank's listing of ineligible firms and individuals). Each record carries the name, address, date the sanction was imposed, the sanction type, the grounds (sanctionable practice or guideline citation) and the listing's record number. Filter by sanction_type or a free-text query. For the main debarment list use debarred-firms.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free-text search matched against the firm/individual name, address and grounds (examples: "cordaid", "armada"; minLength: 1)
• sanction_type string nullable — Only records with this type of sanction (one of: "Letter of reprimand", "Conditional Non-debarment")
• count integer required — Max result count (examples: 20; min: 1)

Response

• @type string (default: "WorldbankOtherSanction")
• name string required
• address string nullable
• sanction_date string nullable
• sanction_type string nullable
• grounds string nullable
• record_number 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.