/bdegp/debarred/search

POST /api/bdegp/debarred/search

Price: 5 credits

Search firms debarred from public procurement on Bangladesh's national e-GP portal, ongoing or all, by firm name, debarment date range or debarring organisation. Each row carries the firm, country, address, the scope of the debarment, its start and end dates with any stay orders, the debarring body and the reasons.

How to use it

Take `department_id` from bdegp/organizations/search to list the debarments one organisation issued.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• status string — Debarments in force now, or every debarment (default: "all"; one of: "all", "ongoing")
• company_name string nullable — Debarred firm name (examples: "engineering"; minLength: 1)
• company_match string — How company_name is matched (default: "contains"; one of: "contains", "equals")
• date_from string nullable — Earliest debarment date (format: date)
• date_to string nullable — Latest debarment date (format: date)
• department_id string nullable — Organisation id (examples: "7"; minLength: 1; pattern: ^\d+$)
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "BdegpDebarment")
• firm_name string required
• country_name string nullable
• address string nullable
• scope_type string nullable
• scope_name string nullable
• start_date string nullable
• end_date string nullable
• stay_orders string nullable
• debarred_by string nullable
• reasons 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.