Indeed API: It Was Shut Down in 2021. Here's What Developers Use Instead

Search "Indeed API" and you'll find documentation for something that no longer exists. Indeed shut down its public job search API in 2021. Developers who built on it woke up to broken integrations and no migration path.

In 2026, there is no official API for querying Indeed job listings. This guide explains exactly what happened, what the remaining Indeed APIs actually do, and the three methods developers use to get job data from Indeed today.

Does Indeed Have an API in 2026?

Indeed does not have a public job search API in 2026. Indeed deprecated its Job Search API in May 2021, with no replacement for data extraction use cases. The only remaining Indeed API is the Publisher API, which is used to embed job listings on third-party job boards — not to extract data.

The short answer: no. Indeed had a public Job Search API that let developers query job listings programmatically. It was shut down in May 2021. No announcement, no replacement, no migration guide. Integrations that relied on it simply stopped working.

The Publisher API is still active but misunderstood. It lets approved partners display Indeed listings in an iframe or widget on their own websites — job boards, HR platforms, career pages. It is not an extraction API. You cannot query it for a CSV of job data. Indeed reviews all Publisher API applications and approves them selectively.

Indeed's CPC model depends on traffic flowing through Indeed.com. An open data API would let developers bypass that entirely — so the economic incentive to kill it was always there.

Why Did Indeed Shut Down Their API?

Indeed shut down its Job Search API in 2021 primarily because its business model depends on job seekers visiting Indeed.com directly — where Indeed earns per-click revenue from employers. An open API allowed developers to surface job listings on third-party platforms without generating revenue for Indeed.

Indeed's revenue comes from employers paying per click when job seekers view or apply to listings on Indeed.com. Every job view that happens outside Indeed.com — through an API integration — is a click Indeed doesn't get paid for.

The Job Search API was originally designed to grow Indeed's reach by embedding listings everywhere. As Indeed became dominant — 350 million monthly searches — the calculus flipped. Keeping traffic on Indeed.com became more valuable than distribution.

The same logic applies to scraping. Indeed actively invests in bot detection because job data is their product. This is why scraping Indeed requires a browser-layer approach rather than server-side HTTP requests.

How Do Developers Get Indeed Job Data Without an API?

Without an official API, developers get Indeed job data through three methods: web scraping with a real browser session (most reliable), third-party data providers like Bright Data or Apify (expensive), or unofficial scraping APIs like ScrapingBee or Oxylabs (mid-range cost and reliability).

Method 1: Browser-Based Scraping (Recommended)

A Chrome extension runs inside your real browser session — after JavaScript has rendered the page, with your actual cookies. Indeed sees normal Chrome traffic. This is the approach Clura uses: navigate to your Indeed search, open the extension, export to CSV. No API key, no proxies, ~4% block rate in our benchmark across 100k+ extractions.

Method 2: Headless Browser (Playwright / Puppeteer)

For automated, unattended pulls — a cron job scraping the same search every morning — Playwright is the code-based option. It renders JavaScript and can navigate pagination. The trade-off: Indeed's CloudFront layer detects headless browser fingerprints at a ~31% rate. You'll need rotating residential proxies to keep block rates manageable.

A basic Playwright setup for Indeed:

Method 3: Third-Party Scraping APIs

Services like Apify, Bright Data, and Oxylabs offer managed Indeed scrapers that handle proxies, fingerprinting, and CAPTCHA solving. You pay per record or per request. Reliable for scheduled automation where you don't want to manage infrastructure.

Is There an Unofficial Indeed API or Endpoint Developers Can Use?

Indeed does have internal API endpoints that its own JavaScript uses to load job cards — you can find them in DevTools Network tab. However, these endpoints use rotating session tokens, require valid browser cookies, and change without notice. Reverse-engineering them is fragile and violates Indeed's Terms of Service.

Open Chrome DevTools → Network tab → filter by Fetch/XHR → reload an Indeed search page. You'll see requests to endpoints like https://www.indeed.com/rpc/jobdescs and similar internal APIs. These are what Indeed's frontend uses to load job cards.

The catch: every request requires a valid _indeedcsrf cookie and session token that Indeed rotates. The endpoints aren't documented. They change between deployments. And using them programmatically violates Indeed's ToS just as scraping does — with the added fragility of undocumented internal APIs.

Reverse-engineering internal APIs is a maintenance nightmare. Every time Indeed deploys, your integration breaks. A browser-based scraper reads the rendered DOM — which stays structurally consistent even when the underlying API changes.

For the full picture on why JavaScript rendering breaks standard HTTP scrapers on Indeed, see how to scrape dynamic websites.

What Data Can You Actually Get from Indeed Without an API?

Without an API, you can extract all publicly visible Indeed job data: job title, company name, location, salary range, job type, date posted, job URL, and the first 2–3 lines of the job description. Full job descriptions require visiting each individual job URL separately.

For most use cases — salary benchmarking, competitor hiring intel, B2B lead generation from job signals — the search results page data is sufficient. For full job descriptions at scale, you need a two-step workflow: scrape search results for URLs, then visit each URL. See the Indeed scraper guide for the full workflow.

Frequently Asked Questions

Does Indeed have a free API?

No. Indeed deprecated its Job Search API in May 2021 and has not released a replacement. The remaining Indeed APIs (Publisher API, Employer API) are not for data extraction. There is no free or paid official API for querying Indeed job listings in 2026.

What replaced the Indeed Job Search API?

Nothing officially replaced it. Developers who need Indeed job data use web scraping — either browser-based tools like Clura, headless browsers like Playwright with residential proxies, or managed scraping APIs like Apify and Bright Data.

Can I use the Indeed Publisher API to extract job data?

No. The Publisher API is for embedding Indeed job listings on third-party websites — it displays an iframe or widget. You cannot use it to programmatically query and download job data. Access is invite-only and restricted to job board partners.

How do I get Indeed job data into a spreadsheet?

The fastest way is a Chrome extension like Clura. Open your Indeed job search, click Clura, and export to CSV in one click. The export includes job title, company, location, salary, date posted, and job URL — one row per listing.

Is scraping Indeed as a replacement for the API legal?

Scraping publicly visible Indeed job postings is generally legal under the hiQ v. LinkedIn ruling (9th Circuit, 2022), which held that accessing public data doesn't violate the CFAA. Indeed's ToS prohibit automated scraping, but ToS violations are civil, not criminal. Operating through a real browser session at human speed minimizes enforcement risk.

Conclusion

The Indeed API is gone and it's not coming back. Building on it in 2021 was a mistake developers are still recovering from.

In 2026, getting Indeed job data means scraping — either through a browser extension for manual exports or Playwright with residential proxies for scheduled automation. The choice depends on volume and whether you need unattended runs.

For most recruiters, HR teams, and sales teams pulling job data weekly, a Chrome extension is the right tool. No infrastructure, no proxy bills, no breakage when Indeed changes its internal endpoints.

Explore related guides:

• Indeed Scraper Guide — how to export Indeed job listings to CSV without code — full step-by-step
• Indeed Scraper Python — why Python scrapers fail on Indeed and what actually works
• Job Listings Scraper Guide — scraping any job board — Indeed, LinkedIn Jobs, Glassdoor — with one workflow
• Scraping Dynamic Websites — why JavaScript-heavy sites like Indeed break HTTP scrapers