/bhtender/opened_bids/search

POST /api/bhtender/opened_bids/search

Price: 1 credit

Search the tender opening results of the Bahrain Tender Board (tenderboard.gov.bh), newest first, by text, purchasing authority, issuer and opening date window. Each row carries the tender number, PA reference, subject, issuer, opening date, purchasing authority and the number of bids.

How to use it

Pass `id` to bhtender/opened_bids for every bidder with its bid value and status, or `tender_id` to bhtender/tenders for the notice. `buyer` takes the authority name exactly as the rows spell it. A row with `tender_id` null (`opening_type` 0, old pre-e-tendering openings — this covers all of 2019 and Jun-Dec 2020, not only years before 2019) answers 412 on bhtender/opened_bids; that row's own fields are the only source for it.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Word or phrase in the tender subject or number (examples: "cleaning"; minLength: 1)
• buyer string nullable — Purchasing authority name (examples: "Bapco Refining"; minLength: 1)
• issuer_type string nullable — Who issued the tender (one of: "External", "Internal")
• opened_from string nullable — Earliest opening date (format: date; examples: "2026-09-01")
• opened_to string nullable — Latest opening date (format: date; examples: "2026-09-15")
• count integer required — Max number of opened tenders to return (min: 1; max: 300)

Response

• @type string (default: "BhtenderOpenedBidSummary")
• id string required
• tender_number string required
• pa_reference string nullable
• name string nullable
• issuer_type string nullable
• opened_date string nullable
• buyer_name string nullable
• bids_count integer nullable
• opening_type string nullable
• envelope string nullable
• tender_id string 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.