# /teamtailor/jobs/search

`POST /api/teamtailor/jobs/search`

Price: 10 credits

List the published job postings of one company's Teamtailor career board, optionally narrowed by free-text query, department, location or employment type. Each row carries the job id, title, hiring organisation, the full HTML description, structured locations, salary range, publication and expiry dates, and the hosted and apply URLs.

## How to use it

Lists one company's board — Teamtailor has no cross-company search, so the handle must already be known. company takes the Teamtailor handle, a board host or a board URL; prefer the handle, since it always resolves. hosted_url and apply_url here echo whichever host was addressed, so a handle yields vendor-host links, while teamtailor/jobs returns the same job on the board's own canonical host; both forms fetch. Rows carry the full description already, but employment type, department and remote status exist only on the detail page, so call teamtailor/jobs with the id for those three. department must match the board's own spelling exactly, including case, while query and employment_type are case-insensitive. A live board with no published postings answers with an empty list, while an unknown handle is a 412.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `company` (string, required) — Company board. Accepts the Teamtailor handle, a board host, or a full board or job URL (examples: "actavo", "instabee.teamtailor.com", "https://careers.actavo.com/jobs"; minLength: 1)
- `count` (integer, required) — Max number of job postings to return (min: 1; max: 1000)
- `query` (string, nullable) — Free-text filter over the board, case-insensitive (examples: "engineer"; minLength: 1)
- `department` (string, nullable) — Filter by department, matched in full and case-sensitively (examples: "Finance", "Engineering"; minLength: 1)
- `location` (string, nullable) — Filter by location (examples: "Dublin", "Stockholm"; minLength: 1)
- `employment_type` (string, nullable) — Filter by employment type, matched case-insensitively (examples: "Contract", "Full-time"; minLength: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "TeamtailorJobSummary")
- `id` (integer, required)
- `company` (string, required)
- `feed_uuid` (string, nullable)
- `company_name` (string, nullable)
- `company_url` (string, nullable)
- `description` (string, nullable)
- `locations` (array) (default: [])
  - `@type` (string) (default: "TeamtailorAddress")
  - `locality` (string, nullable)
  - `region` (string, nullable)
  - `country` (string, nullable)
  - `postal_code` (string, nullable)
  - `street` (string, nullable)
- `salary_range` (object, nullable)
  - `@type` (string) (default: "TeamtailorSalaryRange")
  - `currency` (string, nullable)
  - `interval` (string, nullable)
  - `min` (number, nullable)
  - `max` (number, nullable)
- `published_at` (integer, nullable)
- `valid_through_at` (integer, nullable)
- `hosted_url` (string, nullable)
- `apply_url` (string, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

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

Company board not found, or the host given does not serve a Teamtailor board

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.