Indeed Jobs Feed
Pricing
$4.00 / 1,000 results
Structured job data from Indeed across 62 markets. Full descriptions, parsed salary, employment type, hiring signals, and incremental change tracking for recurring monitoring workflows.
Job search keywords. Single string or JSON array for multi-query (e.g. ["software engineer", "data analyst"]). Required unless startUrls is provided.
Which Indeed domain to search (62 markets). Major markets (US, UK, DE, FR, etc.) are well-tested. Smaller markets are config-supported but listing volume varies.
City, state, or region to search within. Single string or JSON array for multi-location (e.g. ["New York", "San Francisco"]). Leave empty for nationwide results.
Direct Indeed search or job detail URLs. Use instead of or alongside query. Accepts search pages (indeed.com/jobs?q=...) and job pages (indeed.com/viewjob?jk=...).
Maximum total job listings to return across all search sources.
Maximum SERP pages to scrape per search source. Each page typically contains 15 results.
Only return jobs posted within this many days. Automatically snapped to nearest valid value: 1, 3, 7, or 14.
Filter jobs by remote work availability.
Filter by employment type.
Search radius around the specified location. Only applies when location is set. Valid values: 5, 10, 15, 25, 35, 50, 100.
Sort results by relevance (default) or by posting date (newest first).
Fetch each job's detail page for full description, JSON-LD data, requirements, benefits, and hiring signals. Set to false for fast SERP-only scraping.
Output only ~12 core fields (jobId, title, company, location, salary, description, URL, dates, remote status). Ideal for AI agents, MCP workflows, and LLM context windows where token budget matters.
Truncate job descriptions to this many characters (adds '...' suffix). Set to 0 to omit descriptions entirely. Leave empty for full descriptions. Useful for reducing payload size in API integrations and AI pipelines.
Fetch each unique company's /cmp/ page for industry, employee count, headquarters, revenue, and more. Cached per company within each run.
Compare current results against stored state from a previous run. Each job is classified as NEW, UPDATED, UNCHANGED, EXPIRED, or REAPPEARED. Requires stateKey to be set.
Stable identifier for the search universe being tracked. Use a descriptive key like "us-software-nyc" or "de-data-berlin". Different queries/locations should use different keys to avoid state cross-contamination. Required when incrementalMode is true.
When incremental mode is active, also output jobs that haven't changed since the last run. Default: only NEW, UPDATED, and REAPPEARED jobs are emitted.
