# /thaiegp/tenders/search

`POST /api/thaiegp/tenders/search`

Price: 20 credits

Search Thailand e-GP public procurement projects of one fiscal year by name words, contract amount range, procurement method, project type, status, place, procuring department, winner tax id and contract date. Returns the project with budget, reference price, contract amount, buyer and location.

## How to use it

`year` is the Thai fiscal year in the Buddhist Era (Gregorian + 543, starting in October). Pass `id` and `budget_year` of a row to thaiegp/tenders for its contracts, winners and bidders.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `year` (integer, required) — Thai fiscal year (Buddhist Era) (examples: 2569, 2560)
- `query` (string, nullable) — Words of the project name (examples: "โรงพยาบาล"; minLength: 2)
- `contract_amount_range` (string, nullable) — Total contract amount range, THB (one of: "under_200k", "200k_to_2m", "2m_to_10m", "10m_to_100m", "over_100m")
- `method_group` (string, nullable) — Procurement method group (one of: "general", "consultant", "design_supervision")
- `method` (string, nullable) — Procurement method (one of: "electronic_price_competition", "price_competition", "e_market", "design_supervision_agreement", "consultant_selection", "design_supervision_restricted_selection", "special", "design_supervision_selection", "e_bidding", "price_inquiry", "price_agreement", "consultant_agreement", "design_supervision_special_hire", "special_case", "design_supervision_design_contest", "specific", "selection", "consultant_specific", "consultant_open_invitation", "design_or_supervision_open_invitation", "design_or_supervision_specific", "design_or_supervision_selection", "international_bidding")
- `project_type` (string, nullable) — Project type (one of: "purchase", "hire_of_work", "construction", "design", "rent", "consultant", "construction_supervision", "design_and_supervision", "design_and_construction_supervision")
- `status` (string, nullable) — Project status (one of: "in_progress", "contract_ended")
- `area` (string, nullable) — Thai province, district or sub-district name (examples: "เชียงใหม่"; minLength: 2)
- `department_id` (string, nullable) — Procuring department id, as in `department.id` (examples: "3100001")
- `winner_tax_id` (string, nullable) — Contract winner's 13-digit tax id (examples: "0365529000042")
- `project_id` (string, nullable) — Project id (examples: "68049277788")
- `contract_date_from` (string, nullable) — Contract signed on or after (examples: "2026-01-01")
- `contract_date_to` (string, nullable) — Contract signed on or before (examples: "2026-01-31")
- `sort` (string) — Result order (default: "price_desc"; one of: "price_desc", "price_asc", "transaction_date_desc", "transaction_date_asc")
- `offset` (integer) — Rows to skip (default: 0; min: 0; max: 1000)
- `count` (integer, required) — Max number of projects to return (min: 1; max: 5000)

## Response

### 200 — Successful Response

- `@type` (string) (default: "ThaiegpTenderSummary")
- `id` (string, required)
- `name` (string, nullable)
- `budget_year` (integer, nullable)
- `budget_amount` (number, nullable)
- `reference_price` (number, nullable)
- `contract_amount` (number, nullable)
- `announce_date` (string, nullable)
- `transaction_date` (string, nullable)
- `project_type` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `status` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `method_group` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `method` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `organization_type` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `department` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `sub_department` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `province` (object, nullable)
  - `@type` (string) (default: "ThaiegpProvince")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
  - `center_lat` (number, nullable)
  - `center_lon` (number, nullable)
- `district` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `subdistrict` (object, nullable)
  - `@type` (string) (default: "ThaiegpCode")
  - `id` (string, nullable)
  - `name` (string, nullable)
  - `name_en` (string, nullable)
- `location` (string, nullable)
- `location_type` (integer, nullable)
- `lat` (number, nullable)
- `lon` (number, nullable)

## Errors

### 422 — Validation Error

The year is outside the covered range, a date is not YYYY-MM-DD, a tax id is not 13 digits, a project id is not 11 digits, or `area` is not a Thai place name

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

The entity was not found, or a precondition failed

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.