/worldbank/debarred-firms

POST /api/worldbank/debarred-firms

Price: 20 credits

List firms and individuals debarred or cross-debarred by the World Bank Group

How to use it

List the firms and individuals on the World Bank Group's listing of ineligible (debarred and cross-debarred) firms and individuals — the parties barred from being awarded Bank-financed contracts. Each record carries the name, party type (firm/individual), address, country, ineligibility period (from/to dates), grounds (sanctionable practice or guideline citation), debarment status (debarred vs cross-debarred from another multilateral development bank), and the listing's record number. Cross-debarred entries are recognized from the African Development Bank, Asian Development Bank, European Bank for Reconstruction and Development and Inter-American Development Bank. Use debarred-firms/search to filter by name, country, grounds or period.

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 result count (examples: 50; min: 1)

Response

• @type string (default: "WorldbankDebarredFirm")
• id integer required
• name string required
• party_type string nullable
• country string nullable
• country_code string nullable
• city string nullable
• state string nullable
• province string nullable
• postal_code string nullable
• address string nullable
• ineligibility_from string nullable
• ineligibility_to string nullable
• ineligibility_status string nullable
• grounds string nullable
• debarment_status string nullable
• record_number string nullable
• additional_info string nullable
• registration_id 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.