API Reference
Search Indeed job postings by keyword and location and get job detail and location autocomplete as structured JSON. 3 endpoints documented below.
curl "https://api.crawlora.net/api/v1/indeed/search?l=Austin%2C+TX&q=software+engineer" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora's Indeed endpoints return job search, job detail, and location autocomplete as normalized JSON with one API key — no HTML parsing or account required. A pull on 2026-10-27 for data engineer jobs in Austin, TX reported 182 results at 10 per page, and location suggestions came back from a third-party address source.
Send a keyword and location to /indeed/search for normalized job postings.
Pass the job_key from a search result to /indeed/job for that posting's full detail.
Use /indeed/locations/suggest to turn a partial location string into a valid `l` value for /indeed/search.
Re-run searches on a schedule to track new postings and hiring-demand trends across keywords and locations.
search returned total 182 with 10 jobs on page one. Each job has a job_key, title, company, city and state, a salary_text such as $112,597.33 - $152,810.66 a year with a currency code, and a snippet. Page through with page.
locations suggest for Aus returned 5 suggestions, the first a street address (11718 Aus Tex Acres Ln, Austin, TX 78754) from a PRECISELY source. Treat suggestions as address candidates, not clean city names.
/indeed/jobapiKey1 credit/requestReturns one Indeed job posting by its job key (the `job_key` field returned by search).
Required: jk.
Sampled 14 Oct 2026: 15 fields returned with a value. In the sample: posted_at: 2026-06-29; title: “Sr. Backend Engineer”; company_url: indeed.com; description_html: 6,494 characters; company: “dv01”; location: “New York, NY 10003”; city: “New York”; state: “NY”.
/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.
Required: q. Optional: limit.
Sampled 14 Oct 2026: 10 items. Filled in every item: name, source. In the sample: name: “Austin, TX (Travis County)” and 9 other values.
/indeed/searchapiKey1 credit/requestSearches Indeed job postings by keyword and location. `sort` enum: `relevance` (default), `date`.
Required: q. Optional: l, page, sort (2 allowed values: relevance, date), radius, fromage.
Sampled 14 Oct 2026: 10 items. Filled in every item: job_key, title, company, location, salary_currency, salary_text, snippet, posted_at and 1 more. Not in every item: city (9), state (8), postal_code (3). In the sample: posted_at: 2026-09-30 to 2026-10-13; title: “Entry Level Software Engineer 0” and 8 other values; url: indeed.com; snippet: median 303 characters; company: “Power3 Solutions” and 9 other values; location: “Annapolis Junction, MD” and 7 other values; city: “Annapolis Junction” and 6 other values; state: “MD” and 6 other values.
Results from the 7 days to 14 Oct 2026. Current status
| Endpoint | Request | Checks passed | Median response |
|---|---|---|---|
| Indeed location suggestions | GET /indeed/locations/suggest?q=Austin | 100% | 0.14 s |
| Indeed job search | GET /indeed/search?l=Austin%2C+TX&q=software+engineer | 100% | 0.93 s |