/bhtender/tenders/search

POST /api/bhtender/tenders/search

Price: 20 credits

List the tenders of the Bahrain Tender Board e-Tendering system (etendering.tenderboard.gov.bh) at one stage — published, to be opened, opened, awarded or cancelled — newest first, filtered by text, purchasing authority, commodity activity and issuer. Each row carries the tender id, tender and PA reference numbers, title, authority, section, activities, bid bond and its validity, document fee and the stage dates.

How to use it

Pass `id` to bhtender/tenders for the notice, the document purchasers and each bidder's submission status. Bid prices appear on bhtender/opened_bids and winners with amounts on bhtender/awards/search; awarded rows here carry neither.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• status string required — Stage of the tenders to list (one of: "published", "to_be_opened", "opened", "awarded", "cancelled")
• query string nullable — Word or phrase in the title, description or tender number (examples: "cables"; minLength: 1)
• buyer string nullable — Word in the purchasing authority name (examples: "BAPCO"; minLength: 1)
• activity_code string nullable — Commodity activity code (examples: "1074"; minLength: 1)
• issuer_type string nullable — Who issued the tender (one of: "External", "Internal")
• count integer required — Max number of tenders to return (min: 1; max: 5000)

Response

• @type string (default: "BhtenderTenderSummary")
• id string required
• reference string nullable
• pa_reference string nullable
• name string nullable
• description string nullable
• buyer_name string nullable
• section string nullable
• activities array (default: [])
  • @type string (default: "BhtenderActivity")
  • code string nullable
  • name string nullable
• issuer_type string nullable
• bid_bond number nullable
• bond_validity_days integer nullable
• fee number nullable
• document_sale_start_at integer nullable
• document_sale_end_at integer nullable
• bid_closing_at integer nullable
• bid_opening_at integer nullable
• is_opened boolean nullable
• status string required
• details_url 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.