/bhtender/awards/search

POST /api/bhtender/awards/search

Price: 20 credits

The awards of one month from the Bahrain Tender Board monthly award reports (tenderboard.gov.bh): one row per winner with the purchasing authority, tender number, award type, winner and the awarded amount in BHD, filtered by authority and winner name.

How to use it

Authority names and most award types are in Arabic; winners are mostly in English. A tender split between several winners gives one row per winner, and change orders can carry negative amounts. buyer_total_amount is the report's own stated total for that purchasing authority. For 2023-06 and 2023-07, buyer_name and award_type are null on every row and winner_name is present only for English-named winners. A month with no published report answers 412; months before 2021-01 are rejected.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• month string required — Report month (examples: "2026-07"; pattern: ^\d{4}-\d{2}$)
• buyer string nullable — Word in the purchasing authority name (examples: "وزارة"; minLength: 1)
• winner string nullable — Word in the winner name (examples: "PHARMACY"; minLength: 1)
• count integer required — Max number of awards to return (min: 1; max: 1000)

Response

• @type string (default: "BhtenderAward")
• month string required
• buyer_name string nullable
• row_number integer nullable
• tender_number string nullable
• award_type string nullable
• winner_name string nullable
• amount number nullable
• amount_other_currency number nullable
• other_currency string nullable
• currency string required
• buyer_total_amount number nullable
• report_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 award report published for that month 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.