/bhtender/opened_bids

POST /api/bhtender/opened_bids

Price: 5 credits

The opening results of one Bahrain Tender Board tender (tenderboard.gov.bh): subject, description, purchasing authority, category, issuer, invitation method, opening date and every bidder with its bid value, remarks and status.

How to use it

Takes the `id` or `url` of a bhtender/opened_bids/search row. The lowest accepted bid is not necessarily the award; winners with amounts are on bhtender/awards/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• opened_bid_id string required — Opened tender id or its opening results URL (examples: "395/2026/BTB (PP/2026/04)|1", "https://www.tenderboard.gov.bh/OpenedTenderDetails/?id=395%2f2026%2fBTB+(PP%2f2026%2f04)&source=New&envelope=TQ/PB/PQ&type=1"; minLength: 1)

Response

• @type string (default: "BhtenderOpenedBid")
• id string required
• tender_number string nullable
• pa_reference string nullable
• name string nullable
• description string nullable
• buyer_name string nullable
• category string nullable
• issuer_type string nullable
• invitation_method string nullable
• bids_count integer nullable
• request_type string nullable
• opened_date string nullable
• bidders array (default: [])
  • @type string (default: "BhtenderBidder")
  • position integer nullable
  • bidder_name string nullable
  • bid_value number nullable
  • currency string nullable
  • remarks string nullable
  • status 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 — No opening results under that id 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.