API Reference
Use Crawlora's Indeed API endpoints to extract supported public Indeed data as structured JSON. This documentation covers 3 active endpoints including Indeed job detail, Indeed location suggestions, Indeed job search. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as jk, q, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.
Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.
curl -X GET "https://api.crawlora.net/api/v1/indeed/search?q=coffee&page=1&sort=relevance" \
-H "x-api-key: $CRAWLORA_API_KEY"These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.
/indeed/jobapiKey1 credit/requestReturns one Indeed job posting by its job key (the `job_key` field returned by search). Primary transport is Indeed's own credential-free GraphQL API; falls back to the original web-page transport if that fails.
Required params: jk:query
/indeed/locations/suggestapiKey1 credit/requestReturns Indeed's own location-search autocomplete suggestions for a partial location string -- the same suggestions the app's search bar offers -- for building a valid `l` value for search. Credential-free GraphQL only; there is no page-based fallback for this endpoint.
Required params: q:query
/indeed/searchapiKey1 credit/requestSearches 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`.
Required params: q:query
| Endpoint | API path | Method | Credits | Required params | Docs | Playground |
|---|---|---|---|---|---|---|
| Indeed job detail | /indeed/job | GET | 1 credit/request | jk:query | View docs | Try endpoint |
| Indeed location suggestions | /indeed/locations/suggest | GET | 1 credit/request | q:query | View docs | Try endpoint |
| Indeed job search | /indeed/search | GET | 1 credit/request | q:query | View docs | Try endpoint |