/bdegp/awards/search

POST /api/bdegp/awards/search

Price: 5 credits

Search contract awards on Bangladesh's national e-GP portal, latest contract signing date first, optionally by keyword. Each row is one awarded lot: tender ID, reference, package title and advertisement time, ministry, procuring entity and method, district, contract signing date, supplier and contract value in crore taka.

How to use it

`contract_value_crore` is in crore taka (1 crore = 10,000,000 BDT), rounded to three decimals, so read the exact contract price from bdegp/awards, passing both the row's `tender_id` and its `id`.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Words to search for (examples: "supply", "bridge"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "BdegpAwardSummary")
• id string required
• tender_id string required
• reference string nullable
• name string nullable
• advertised_at integer nullable
• ministry string nullable
• buyer_name string nullable
• procurement_method string nullable
• district string nullable
• contract_signed_date string nullable
• supplier_name string nullable
• contract_value_crore number 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 — 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.