Indeed API: how to pull job postings from Indeed without scraping

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 and how to pull Indeed job postings the modern way — by title, location, salary band, and posted-after — through a single normalized REST endpoint.

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 theirpublisher.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 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 \
  -H "Authorization: Bearer $JOBSPIPE_KEY" \
  -G \
  -d "source=indeed" \
  -d "query=senior react" \
  -d "location=San Francisco" \
  -d "salary_min=180000" \
  -d "posted_after=7d"

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.

Compared to 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.

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 collapses these into one canonical record so your customers don’t see triplicates.