# Indeed Job Search

> Indeed US job listings as JSON: title, company, location, salary range, rating, link

- Vendor: `indeedjobsearch` · version 1.0 · category Jobs · tags indeed, us jobs, job search, salaries, recruitment data
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/indeedjobsearch
- This document: https://apiclay.com/docs/indeedjobsearch.md
- OpenAPI 3.1: https://apiclay.com/api/indeedjobsearch/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `indeedjobsearch`
- Updated: 2026-11-18

## About

## Indeed Job Search

Search US job listings on Indeed and get clean JSON.

### Route

#### /jobs

Jobs for a search: job_key, title, company, location, salary (as shown), salary_min, salary_max, salary_period (YEARLY, HOURLY ...), job_types, company_rating, company_reviews, posted, remote, url. About 15 to 45 per page; use start (0, 10, 20 ...) for more. Rendered in a browser (adds the platform browser fee).

```bash
curl -G 'https://api.apiclay.com/v1/api/indeedjobsearch/jobs' -H 'token: YOUR_TOKEN' --data-urlencode 'q=data analyst' --data-urlencode 'l=Chicago, IL'
```

### Notes

Data comes from public Indeed search pages (indeed.com, United States). Not affiliated with Indeed.

## Pricing

- Pay as you go: 0.01 credits/request
- Trial: 10 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.
- Browser rendering (0.005 credits per rendered call): A call that renders the page in a browser adds the browser fee to the route price: routes with render mode js, routes with render mode auto when the call switches to the browser (pre-charged, refunded when it does not), and calls sent with `X-ApiClay-Render: js`.
- Trial and plan requests still pay the browser fee.
- Response headers on a billed call: `X-ApiClay-Browser-Fee`.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /jobs — Job search
- Gateway: `GET https://api.apiclay.com/v1/api/indeedjobsearch/jobs`
- Public query params: `q` (string, required), `l` (string), `start` (string)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 5.8 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/indeedjobsearch/jobs?q=<q>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
