/omantender/tenders/search

POST /api/omantender/tenders/search

Price: 10 credits

List the tenders of the Oman Tender Board e-Tendering system (etendering.tenderboard.gov.om) at one stage — published, open, awarded or cancelled — filtered by government entity, procurement category and sub-category, grade, tender type, text and date window. Each row carries the tender id, tender number, name, description, entity, category and grades, tender type, the stage date, tender fee and bank guarantee.

How to use it

On published and open tenders `query` matches the English tender name; on awarded and cancelled tenders it matches the Arabic name or the tender number. The date window applies to the submission deadline, the opening date, the award date or the cancellation date, following `status`. `subcategory` is a code inside `category` (602, cleaning, under Z6). Pass `id` to omantender/tenders for the notice, the opened bids with their prices and the document purchasers; awarded rows carry no award value and no winner.

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", "open", "awarded", "cancelled")
• query string nullable — Word or phrase in the tender name; on awarded and cancelled tenders also the tender number (examples: "Supply"; minLength: 1)
• buyer_code string nullable — Code of the government entity (examples: "MOH"; minLength: 1)
• category string nullable — Procurement category (one of: "Z1", "Z2", "Z3", "Z4", "Z5", "Z6", "Z7", "Z8", "C1", "G", "C2", "T1", "I1")
• subcategory string nullable — Procurement sub-category code (examples: "602"; minLength: 1)
• grade string nullable — Supplier grade the tender is open to (one of: "1", "2", "3", "4", "5")
• tender_type string nullable — Tender type (one of: "1", "2", "4", "5", "6", "7", "8", "9")
• procurement_kind string nullable — Tenders or purchase orders (one of: "NON_DG", "RFQ")
• date_from string nullable — Start of the stage date window (format: date; examples: "2026-09-01")
• date_to string nullable — End of the stage date window (format: date; examples: "2026-09-30")
• subcontracts boolean — List sub-contract tenders instead of main tenders (default: false)
• count integer required — Max number of tenders to return (min: 1; max: 1000)

Response

• @type string (default: "OmantenderTenderSummary")
• id string required
• tender_number string nullable
• name string nullable
• description string nullable
• buyer_name string nullable
• procurement_category string nullable
• grades array (default: [])
• tender_type string nullable
• bidder_origin string nullable
• document_sale_end_date string nullable
• submission_deadline_date string nullable
• opened_at integer nullable
• awarded_at integer nullable
• cancelled_at integer nullable
• fee number nullable
• bank_guarantee string nullable
• bidders_disclosed boolean nullable
• parent_tender_number string nullable
• parent_tender_name string nullable
• status 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 — 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.