/bhtender/tenders

POST /api/bhtender/tenders

Price: 5 credits

One tender of the Bahrain Tender Board e-Tendering system (etendering.tenderboard.gov.bh) by id: English and Arabic title and description, purchasing authority, CPV codes, contract duration, evaluation type, invitation method, commodity activities, SME flag, envelope type, bid validity, document fee, bid bond, the full schedule, the document purchasers and each bidder's submission status.

How to use it

Takes the `id` of a bhtender/tenders/search row, or the `tender_id` of a bhtender/opened_bids/search row. Bid prices are on bhtender/opened_bids and award amounts 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)
• tender_id string required — Tender id or its notice URL (examples: "11588", "https://etendering.tenderboard.gov.bh/Tenders/nitParameterView?mode=public&tenderNo=11588&PublicUrl=1"; minLength: 1)

Response

• @type string (default: "BhtenderTender")
• id string required
• reference string nullable
• pa_reference string nullable
• request_type string nullable
• name string nullable
• name_ar string nullable
• description string nullable
• description_ar string nullable
• buyer_name string nullable
• published_date string nullable
• issuer_type string nullable
• cpv_codes array (default: [])
• contract_duration string nullable
• evaluation_type string nullable
• invitation_method string nullable
• procurement_category string nullable
• procurement_subcategories array (default: [])
• activities array (default: [])
  • @type string (default: "BhtenderActivity")
  • code string nullable
  • name string nullable
• supplier_grades array (default: [])
• prebid_clarification string nullable
• is_sme_only boolean nullable
• envelope_type string nullable
• alternative_bids_allowed boolean nullable
• bid_validity_days integer nullable
• bid_validity_end_at integer nullable
• fee number nullable
• fee_payment_method string nullable
• bid_bond number nullable
• document_sale_start_at integer nullable
• document_sale_end_at integer nullable
• clarification_start_at integer nullable
• clarification_end_at integer nullable
• bid_closing_at integer nullable
• price_opening_at integer nullable
• purchasers array (default: [])
  • @type string (default: "BhtenderPurchaser")
  • registration_number string nullable
  • company_name string nullable
  • purchased_at integer nullable
• bidder_statuses array (default: [])
  • @type string (default: "BhtenderBidderStatus")
  • bid_number string nullable
  • company_name string nullable
  • purchased_at integer nullable
  • submission_status string nullable
• bids_submitted_count integer nullable
• document_buyers_count integer nullable
• currency 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 — No public tender 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.