[NewSearch millions of jobs from your AI agent with MCP→](/blog/jobspipe-mcp-server) [All posts](/blog) Guide·Jul 13, 2026·8 min read # Indeed API: how to pull job postings from Indeed without scraping Indeed's Publisher API is gone and the official replacements are employer-side only. What the Indeed API actually is in 2026, why there is no self-serve API key, and how to query Indeed job postings through a normalized JSON endpoint instead. ![Dvir Atias](/authors/dvir-atias.jpg) Dvir Atias Founder, JobsPipe Indeed deprecated their official Publisher API in 2023. Since then, most posts about the “**Indeed API**” either point at a 410 Gone page, suggest scraping (against Indeed’s TOS and operationally fragile), or push readers toward enterprise-tier partnerships that take months to close. This post covers what’s actually available in 2026 - the employer-side APIs Indeed still ships, why none of them return job postings, and how to pull Indeed job postings the modern way - by title, location, salary band, and posted-after - through a single normalized REST endpoint. ## Does Indeed have an API in 2026? Yes, but not the one most developers are looking for. Every official Indeed API is employer-side: built for pushing jobs and applications _into_ Indeed, not for reading job postings out. The current official surfaces are: - **Job Sync API** - a GraphQL API for ATS partners to publish and update their clients’ jobs on Indeed. - **Indeed Apply** - delivers applications from Indeed’s hosted apply flow back into a partner ATS. - **Disposition Sync API** - reports candidate outcomes back to Indeed so employer analytics stay accurate. - **Sponsored Jobs API** - campaign management for agencies running Indeed ad spend. All four are gated behind Indeed’s partner program, and none of them exposes a search-jobs endpoint. If your goal is reading postings - for a job board, a sourcing tool, or market analysis - the official Indeed APIs are a dead end by design. ## What happened to the Publisher API The Publisher API was Indeed’s public XML feed for affiliates. It returned a list of jobs by query and was free to use with API key registration. Indeed shut it down in 2023 in favor of their`publisher.indeed.com` hosted-search widget (which is iframe-only, not data-accessible) and a separate enterprise data partnership program (NDA-gated, sales-led, six-figure minimums). For most developers - building a job board, an AI sourcing tool, or a compensation product - neither option is a fit. ## How to get an Indeed API key There is no self-serve Indeed API key. The old Publisher API keys stopped working with the 2023 shutdown, and the current partner APIs issue credentials only after approval into the partner program - a sales-led process aimed at ATSs and staffing platforms, not at data consumers. Tutorials that still walk you through “registering for an Indeed publisher key” predate the deprecation. For reading job postings, the practical equivalent is a key for an API that indexes Indeed’s public listings - which is what JobsPipe’s Indeed source is. ## How to query Indeed jobs through JobsPipe JobsPipe indexes Indeed’s public search results and serves them through one endpoint, with the same normalized schema as every other source: ``` curl https://api.jobspipe.dev/v1/jobs/search \ -H "Authorization: Bearer jp_live_your_key_here" \ -H "Content-Type: application/json" \ -d '{ "source_or": ["indeed"], "job_title_or": ["senior react"], "job_country_code_or": ["US"], "posted_at_max_age_days": 7 }' ``` The response includes a `compensation` object parsed from the description, a stable `id` that doesn’t change across crawls, and an `apply_url` pointing back at the original Indeed listing. ## Indeed API vs scraping Indeed yourself Indeed uses heavy bot management - Cloudflare + a custom challenge layer. DIY scrapers get blocked within hours of going to production unless you’re rotating across hundreds of residential IPs. Maintenance is constant: Indeed re-skins their listing pages roughly every 8 weeks. JobsPipe handles all of that on our side. You pay $49/mo for 100,000 requests; the equivalent DIY pipeline (proxies + maintenance + on-call time) clears $3,000/mo for any team running it seriously. We ran the full build-vs-buy math in [Indeed scraper vs Indeed API](/blog/indeed-scraper-vs-api). ## Combine Indeed with other sources The reason a unified jobs API matters more than a single-source scraper: the same job often appears on Indeed, Glassdoor, and the original Greenhouse listing simultaneously. JobsPipe’s [cross-source dedup](/blog/ai-salary-parsing-structured-ranges) collapses these into one canonical record so your customers don’t see triplicates. Get started with the Indeed source in 30 seconds - free tier included. [ ← Previous What is a SERP API? How they work and when to use one ](/blog/what-is-a-serp-api)[ Next → How to scrape Google Jobs in Python (and the no-scrape alternative) ](/blog/google-jobs-scraper) --- Canonical URL: https://jobspipe.dev/blog/indeed-api-guide Title: Indeed API: how to pull job postings from Indeed without scraping Description: Indeed's Publisher API is gone and the official replacements are employer-side only. What the Indeed API actually is in 2026, why there is no self-serve API key, and how to query Indeed job postings through a normalized JSON endpoint instead.