Endpoint Playground
Searches Indeed job postings by keyword and location. `sort` enum: `relevance` (default), `date`.
14 Oct 2026: 10 jobs; 9 fields had a value in every checked item and 3 varied between items.
Sample value profiles: posted_at: 2026-09-30 to 2026-10-13; title: “Entry Level Software Engineer 0” and 8 other values; url: indeed.com.
curl 'https://api.crawlora.net/api/v1/indeed/search?q=software+engineer&sort=relevance' \
-H "x-api-key: $CRAWLORA_API_KEY"| Parameter | Type | Required | Prefilled value | Description |
|---|---|---|---|---|
| q | string | Yes | software engineer | Search keywords |
| l | string | No | Location (city, state, or zip) | |
| page | integer | No | Page number, 1-based, defaults to 1 | |
| sort | string | No | relevance | Sort order: relevance, date |
| radius | integer | No | Search radius in miles | |
| fromage | integer | No | Only jobs posted within this many days |
{
"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"
}
]
}
}The sample response, schema and code snippets below work without an account. Sending a live request needs an API key.