# /yourator/jobs/search

`POST /api/yourator/jobs/search`

Price: 1 credit

Search job listings on Yourator (yourator.co), the Taiwan startup and tech job board, by keyword, job category, city, employment type, remote arrangement and salary range. Each job carries its salary as shown on the site, city, activity label, skill tags, external apply link and the hiring company with its logo and badges.

## How to use it

Pass a job id to yourator/jobs for the full description, requirements, benefits and salary range.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `count` (integer, required) — Max number of jobs to return (min: 1; max: 2000)
- `keyword` (string, nullable) — Search words (examples: "python"; minLength: 1)
- `categories` (array, nullable) — Job categories (one of: "商業開發", "通路開發", "實體經營", "市場分析", "銷售業務", "行銷企劃 / 社群經營", "編輯 / 內容經營", "廣告創意 / 企劃", "攝影 / 影音製作", "Growth Hacker", "媒體公關 / 宣傳採買", "MIS / 網路管理", "通訊電信", "教育 / 教學", "外語高手", "其他", "專案 / 產品管理", "UIUX / 視覺設計", "韌體 / 電子電路", "硬體工程", "半導體", "前端工程", "後端工程", "全端工程", "行動裝置開發", "遊戲開發", "測試工程", "DevOps / SRE", "資料工程 / 機器學習", "人資", "財務 / 會計", "行政", "營運", "客戶服務", "法務", "光電工程", "研究人員", "3D / 動畫設計", "資安工程師", "Android 工程師", "iOS 工程師", "資料庫", "區塊鏈工程師", "AR / VR 工程師", "客服工程師", "軟體工程師", "資料科學家", "數據 / 資料分析師", "大數據工程師", "AI 工程師", "資安分析師", "資安架構師", "滲透測試工程師", "雲端工程師", "系統架構師", "應用工程師 / FAE", "採購")
- `areas` (array, nullable) — City or county codes, or oversea (one of: "TPE", "NWT", "TAO", "TXG", "TNN", "KHH", "KEE", "HSZ", "HSQ", "MIA", "YUN", "CHA", "NAN", "CYI", "CYQ", "ILA", "HUA", "TTT", "PIF", "PEN", "KIN", "LIE", "oversea")
- `positions` (array, nullable) — Employment types (one of: "full_time", "part_time", "contract", "temporary", "intern", "others")
- `remote` (array, nullable) — Remote work arrangements (one of: "none", "partial", "full")
- `salary_period` (string, nullable) — Salary period for the salary bounds (one of: "monthly", "annual", "hourly")
- `salary_min` (integer, nullable) — Minimum salary in TWD (examples: 60000; min: 0)
- `salary_max` (integer, nullable) — Maximum salary in TWD (examples: 120000; min: 0)
- `sort` (string, nullable) — Result order (one of: "recent_updated", "most_related")

## Response

### 200 — Successful Response

- `@type` (string) (default: "YouratorJob")
- `id` (string, required)
- `url` (string, required)
- `summary` (string, nullable)
- `category` (string, nullable)
- `salary_text` (string, nullable)
- `salary` (object, nullable)
  - `@type` (string) (default: "YouratorSalary")
  - `min` (number, nullable)
  - `max` (number, nullable)
  - `currency` (string, required)
  - `period` (string, nullable)
  - `is_negotiable` (boolean, required)
- `location` (string, nullable)
- `activity_text` (string, nullable)
- `tags` (array) (default: [])
- `apply_url` (string, nullable)
- `apply_platform` (string, nullable)
- `is_pinned` (boolean, nullable)
- `company` (object, nullable)
  - `@type` (string) (default: "YouratorCompanyRef")
  - `id` (string, nullable)
  - `alias` (string, required)
  - `url` (string, required)
  - `name` (string, nullable)
  - `image` (string, nullable)
  - `banner` (string, nullable)
  - `badges` (array) (default: [])

## Errors

### 422 — Validation Error

An unknown enum value, or salary bounds without salary_period

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.