Indeed job search API

Endpoint facts

Method

GET

API path

/indeed/search

Auth

apiKey

Credits

1 credit/request

Platform

Indeed

Response schema

#/definitions/indeed.searchResponseDoc

Overview

Searches Indeed job postings by keyword and location. Primary transport is Indeed's own credential-free GraphQL API; a page 1, unfiltered-by-date request uses it directly. Requesting page 2+ or the `fromage` filter (not yet expressible over the primary transport) uses the original web-page transport instead, with the same normalized response shape either way. `sort` enum: `relevance` (default), `date`. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- A valid query with no matches returns `total: 0` and an empty `jobs` array (not an error). - `jobs[].company_rating` / `jobs[].company_review_count` / `jobs[].job_types` / `jobs[].posted_relative` / `jobs[].sponsored` / `jobs[].urgently_hiring` / `jobs[].new_job` / `jobs[].indeed_applyable` / `jobs[].salary_min` / `jobs[].salary_max` are only populated when the web-page transport served the response — they are not currently selected from the GraphQL API and so are omitted on a page-1 GraphQL response. `salary_text` and `salary_currency` are populated on both transports. - `jobs[].snippet` on a GraphQL-served response is the job description truncated to roughly 300 characters, not Indeed's own SERP-highlighted snippet. - `jobs[].url` is always the canonical `https://www.indeed.com/viewjob?jk=...` link, not an upstream apply-through redirect. - An invalid `sort` value returns a `400` invalid-params error rather than being silently dropped. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "software engineer", "location": "Austin, TX", "page": 1, "total": 3040, "jobs": [ { "job_key": "5e52165ce276aa5a", "title": "Staff HPC Applications Engineer", "company": "NextSilicon", "location": "Austin, TX", "city": "Austin", "state": "TX", "posted_at": "2026-08-03T05:00:00Z", "url": "https://www.indeed.com/viewjob?jk=5e52165ce276aa5a" } ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related