/worldbank/debarred-firms/search

POST /api/worldbank/debarred-firms/search

Price: 20 credits

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

How to use it

Search the World Bank Group's listing of ineligible (debarred and cross-debarred) firms and individuals — the parties barred from being awarded Bank-financed contracts — for compliance screening. Match a name or address with query, and narrow by country, grounds (sanctionable practice such as Fraudulent/Corrupt/Collusive Practice, a cross-debarment source like EBRD/ADB/IDB/AfDB, or a guideline citation), party type (firm or individual), debarment status (debarred vs cross-debarred), and the ineligibility period. Each match returns the full record (name, address, country, ineligibility from/to dates, grounds, status and record number). Returns an empty list when nothing matches.

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 listing notes (examples: "norcontrol", "construction"; minLength: 1)
• country string nullable — Only records from this country (examples: "Ukraine", "India", "Peru"; minLength: 1)
• grounds string nullable — Only records whose grounds contain this text — the sanctionable practice (e.g. 'Fraudulent Practice', 'Corrupt Practice'), a cross-debarment source (e.g. 'EBRD', 'ADB', 'IDB', 'AfDB'), or a guideline citation (examples: "Fraudulent Practice", "Cross Debarment", "Corrupt"; minLength: 1)
• party_type string nullable — Only records of this party type (one of: "F", "I", "U", "C")
• debarment_status string nullable — Only records with this debarment status — debarred directly by the World Bank, or cross-debarred from another multilateral development bank (one of: "D", "X")
• ineligibility_from_after string nullable — Only records whose ineligibility start date is on or after this date (YYYY-MM-DD) (examples: "2020-01-01")
• ineligibility_to_before string nullable — Only records whose ineligibility end date is on or before this date (YYYY-MM-DD) (examples: "2030-12-31")
• count integer required — Max result count (examples: 20; 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.