# /gebiz/tenders/search

`POST /api/gebiz/tenders/search`

Price: 20 credits

Search Singapore government procurement opportunities on GeBIZ by title words, document number, agency reference, agency, opportunity type, procurement category, GRA head and the published, closing and award date ranges, read from the open listing or from a closed-status facet. Each result carries the document number, reference, kind, title, status, agency, procurement category, published and closing dates and the submission mode.

## How to use it

`status` picks the listing being read: `open` (the default) lists opportunities still accepting bids, `closed` every closed one, and `pending_award`, `awarded`, `cancelled`, `no_award` and `closed_only` the site's own facets of the closed listing — an award search is `status=awarded` with `awarded_from`/`awarded_to`. A `document_number` or `reference` lookup is answered from whichever tab holds the record, so `status` may be left at its default. `sort` reorders the listing (`published_newest`, `closing_soonest`, `relevance`); unset, rows come in the listing's own order. `agencies`, `categories` and `gra_heads` take the site's own ids and codes, not names; an id outside the catalogue is rejected. Bids, awarded suppliers and values live on gebiz/tenders, keyed by `id`.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `title_all` (string, nullable) — Words that must all appear in the title (examples: "maintenance"; minLength: 1)
- `title_any` (string, nullable) — Words of which at least one must appear in the title (examples: "cleaning laundry"; minLength: 1)
- `title_none` (string, nullable) — Words that must not appear in the title (examples: "renewal"; minLength: 1)
- `title_exact` (string, nullable) — Exact phrase in the title (examples: "estate management"; minLength: 1)
- `document_number` (string, nullable) — GeBIZ document number (examples: "PUB000ETT26000037"; minLength: 1)
- `reference` (string, nullable) — Agency reference number (examples: "JO/33260045"; minLength: 1)
- `agencies` (array) — GeBIZ agency ids (default: []; examples: ["2015000000000000098"])
- `opportunity_types` (array) — Opportunity types (default: []; one of: "AU", "PQ", "TQ", "RF", "TT", "TL"; examples: ["TT","TQ"])
- `categories` (array) — GeBIZ procurement category ids (default: []; examples: ["100017"])
- `gra_heads` (array) — Government Registration Authority supply or work head codes (default: []; examples: ["CR01"])
- `published_from` (string, nullable) — Earliest published date (examples: "2026-09-01")
- `published_to` (string, nullable) — Latest published date (examples: "2026-09-21")
- `closed_from` (string, nullable) — Earliest closing date (examples: "2026-08-01")
- `closed_to` (string, nullable) — Latest closing date (examples: "2026-08-31")
- `awarded_from` (string, nullable) — Earliest award date (examples: "2026-07-01")
- `awarded_to` (string, nullable) — Latest award date (examples: "2026-07-31")
- `status` (string) — Listing tab or facet the results are read from (default: "open"; one of: "open", "closed", "closed_only", "pending_award", "awarded", "cancelled", "no_award")
- `sort` (string, nullable) — Result order; awarded_newest is offered on status=awarded only (one of: "relevance", "published_newest", "closing_soonest", "awarded_newest"; examples: "published_newest")
- `count` (integer, required) — Max number of results (min: 1; max: 1000)
- `offset` (integer) — How many matches to skip before the first returned row (default: 0; min: 0; max: 999)

## Response

### 200 — Successful Response

- `@type` (string) (default: "GebizTenderSummary")
- `id` (string, required)
- `reference` (string, nullable)
- `kind` (string, nullable)
- `status` (string, nullable)
- `buyer` (object, nullable)
  - `@type` (string) (default: "GebizBuyer")
  - `name` (string, required)
  - `address` (string, nullable)
- `category` (string, nullable)
- `published_at` (integer, nullable)
- `deadline_at` (integer, nullable)
- `submission_mode` (string, nullable)
- `country` (string) (default: "SG")
- `url` (string, required)

## Errors

### 422 — Validation Error

A date was not YYYY-MM-DD, or an agency, category or GRA head value is not in the catalogue.

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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 GeBIZ opportunity matched those filters on the requested status.

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.