/omantender/tenders

POST /api/omantender/tenders

Price: 5 credits

One tender of the Oman Tender Board e-Tendering system (etendering.tenderboard.gov.om) by id: the notice (entity, tender number, Arabic and English name, evaluation and tender type, category and sub-categories, eligible grades, governorate and wilayat, envelope type, fee, bank guarantee and the full schedule), the opened bids with bidder, offer type and total price, the document purchasers and each bidder's submission status.

How to use it

Takes the `id` of an omantender/tenders/search row. Bids appear once the envelopes are opened; the award value and the winning bidder are not published, so the lowest opened price is not necessarily the award.

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: "95932", "https://etendering.tenderboard.gov.om/product/nitParameterView?mode=public&tenderNo=95932&PublicUrl=1"; minLength: 1)

Response

• @type string (default: "OmantenderTender")
• id string required
• tender_number string nullable
• name string nullable
• name_en string nullable
• buyer_name string nullable
• published_date string nullable
• evaluation_type string nullable
• tender_type string nullable
• procurement_category string nullable
• procurement_subcategories array (default: [])
• grades array (default: [])
• pre_bid_queries string nullable
• governorate string nullable
• wilayat string nullable
• envelope_type string nullable
• alternative_offers_allowed boolean nullable
• fee number nullable
• fee_payment_method string nullable
• bank_guarantee string nullable
• document_sale_start_at integer nullable
• document_sale_end_at integer nullable
• queries_start_at integer nullable
• queries_end_at integer nullable
• submission_deadline_at integer nullable
• technical_opening_at integer nullable
• financial_opening_at integer nullable
• bids array (default: [])
  • @type string (default: "OmantenderBid")
  • position string nullable
  • bidder_name string nullable
  • offer_type string nullable
  • total_price number nullable
  • status string nullable
• purchasers array (default: [])
  • @type string (default: "OmantenderPurchaser")
  • registration_number string nullable
  • company_name string nullable
  • company_type string nullable
  • purchased_at integer nullable
• bidder_statuses array (default: [])
  • @type string (default: "OmantenderBidderStatus")
  • 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
• 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.