# /jobvite/jobs/search

`POST /api/jobvite/jobs/search`

Price: 10 credits

List the open job postings of one company's Jobvite career board by board slug, optionally narrowed by keyword, category, region, location or employment type. Each row carries the job id, title, location and the posting URL.

## How to use it

Lists one company's board — Jobvite has no cross-company search and publishes no directory, so the board slug must come from a URL and is not the display name ('pathways' renders as Clarvida). category, region, location and employment_type are vocabularies each board defines for itself and must match the board's own string exactly, because upstream ignores a value it does not recognise instead of erroring. Each of them is therefore checked by re-running the search without it: if dropping it changes nothing the call is a 422 naming that field, which almost always means a misspelling rather than no results — but it also fires when the value legitimately covers every posting the other filters left, so a 422 on a value you took from a posting means drop that filter, not that it is wrong. query is free text, is not checked this way and can legitimately return nothing. Rows are a summary; call jobvite/jobs with the id for the description, category and dates.

## 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 slug from the career-page URL (jobs.jobvite.com/{company}) (examples: "innio", "nutanix", "pathways"; minLength: 1)
- `count` (integer, required) — Max number of job postings to return (min: 1; max: 1000)
- `query` (string, nullable) — Free-text keyword search over the postings (examples: "engineer", "nurse"; minLength: 1)
- `category` (string, nullable) — Category the board defines, spelled exactly as the board spells it (examples: "Engineering", "Sales"; minLength: 1)
- `region` (string, nullable) — Region the board defines, spelled exactly as the board spells it (examples: "Austria", "United States"; minLength: 1)
- `location` (string, nullable) — Location the board defines, spelled exactly as the board spells it (examples: "Austria - Jenbach", "Savannah, Georgia"; minLength: 1)
- `employment_type` (string, nullable) — Employment type the board defines, spelled exactly as the board spells it (examples: "Experienced", "Internship"; minLength: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "JobviteJobSummary")
- `id` (string, required)
- `company` (string, required)
- `location` (string, nullable)
- `url` (string, nullable)

## Errors

### 422 — Validation Error

A category, region, location or employment_type value that did not narrow the board — usually a value this board does not define, but also raised when the value is genuinely true of every posting the other filters left

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

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.