/bdegp/tenders/search

POST /api/bdegp/tenders/search

Price: 5 credits

Search tenders on Bangladesh's national e-GP portal by status, procurement nature, type and method, tender ID, exact reference, publication and closing date ranges, framework agreements, category, organisation and procuring entity office, or by keyword. Each row carries the tender ID, reference, status, title, the ministry-to-procuring-entity chain, type, method and publication and closing times.

How to use it

Send `keyword` alone, because it cannot be combined with any other filter. Take `department_id` from bdegp/organizations/search and `office_id` from bdegp/offices/search; a department matches only its own tenders, not those of its child organisations. Tenders run by request for quotation (RFQ, RFQU, RFQL), limited tendering or direct procurement are not listed; bdegp/awards/search and bdegp/experience/search rows carry their `tender_id`. Pass a row's `id` to bdegp/tenders for lots, dates, fees and the inviting official.

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 across every tender status (examples: "supply"; minLength: 1)
• status string — Tender status (default: "all"; one of: "all", "live", "archive", "cancelled")
• procurement_nature string nullable — Procurement nature (one of: "goods", "works", "services", "physical_services")
• procurement_type string nullable — National (NCT) or international (ICT) competitive tendering (one of: "nct", "ict")
• procurement_method string nullable — Procurement method (one of: "otm", "ostetm", "qcbs", "ic", "sfb", "sbcq", "lcs")
• tender_id string nullable — Tender ID (examples: "1317342"; minLength: 1; pattern: ^\d+$)
• reference string nullable — Exact invitation reference number, without a comma (examples: "GSTU/PDW/2026-27/Bus/Tyre/02"; minLength: 1)
• published_from string nullable — Earliest publication date (format: date)
• published_to string nullable — Latest publication date (format: date)
• closing_from string nullable — Earliest closing date (format: date)
• closing_to string nullable — Latest closing date (format: date)
• is_framework boolean nullable — Framework agreement tenders only, or none of them
• category string nullable — Procurement category name (examples: "Construction work"; minLength: 1)
• department_id string nullable — Organisation id (examples: "138"; minLength: 1; pattern: ^\d+$)
• office_id string nullable — Procuring entity office id (examples: "2160"; minLength: 1; pattern: ^\d+$)
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "BdegpTenderSummary")
• id string required
• reference string nullable
• status string nullable
• amendments_count integer nullable
• name string nullable
• procurement_nature string nullable
• is_framework boolean nullable
• ministry string nullable
• buyer_name string nullable
• buyer_hierarchy array (default: [])
• procurement_type string nullable
• procurement_method string nullable
• published_at integer nullable
• closing_at integer 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.