Back to blog
· 6 min read

Is There an Indeed API? Job Search API Status in 2026

indeedAPIjobsweb scrapingpython

The short answer

No public Indeed API lets you search or read job listings today. The old Publisher Jobs API did, but Indeed deprecated it and closed it to new integrations by 2023. What remains are partner APIs for platforms that post their clients’ jobs, plus a Hiring Lab API for aggregate labor-market statistics. For individual listings, you read Indeed’s public search pages, yourself or through a scraper you call like an API.

OptionWho can use itGives you Indeed job listings to read?
Publisher Jobs API (Job Search, Get Job)Nobody new: deprecated, closed to new integrationsNo longer
Job Sync API and Job Update APIApproved ATS partners and agenciesOnly jobs of the employers you’re authorized for
Hiring Lab APIResearchers and partners, key on requestNo: aggregated indices, not postings
Scraping public search pagesAnyoneYes, everything a visitor can see

What Indeed’s official APIs actually cover

The Publisher program, then and now. Anyone could once open a free Publisher account, get a publisher ID and call the Job Search API to show Indeed results on their own site, earning money on the traffic. By August 2023, Indeed’s developer site listed it as “Publisher Jobs API (Legacy)”, with both the Job Search and Get Job endpoints marked deprecated and “not available for new integrations”. The endpoint’s host, api.indeed.com, no longer resolves, and the old developer site now redirects to Indeed’s partner portal. Tutorials built on that API are dead ends.

The partner APIs. Indeed’s current APIs all point the same way: data flows from employers’ systems into Indeed. The Job Sync API is “a GraphQL API for ATS partners to create, upsert, expire, and check the status of job postings on Indeed”. Access requires a developer agreement and Indeed’s approval, and Indeed puts a typical integration at about six weeks. The Job Update API lets partners and ad agencies list and update postings, but only those of the employer on your access token. Candidate Sync and Disposition Sync move application data to and from an ATS. None of them is a job search API.

Hiring Lab data. The Hiring Lab API serves the labor-market data Indeed’s research team publishes: job postings indices (February 1, 2020 = 100), wage growth, remote work and AI-related postings, by country, region or sector. Keys are issued by email after Indeed reviews your use case. Good for trend lines, but it holds no individual jobs.

Why scraping public pages is the usual route

Every Indeed search result is visible without an account. Scraping means requesting those pages programmatically and turning them into structured records, the only practical way to get listing-level data now that the Publisher API is gone. For the trade-offs in general, see our API vs web scraping comparison.

It is not trivial:

  • Anti-bot checks. Indeed inspects the TLS fingerprint of your HTTP client and flags datacenter IPs quickly, so a plain HTTP script tends to get blocked. Residential proxies are the norm.
  • Pagination. Results come a page at a time, so a deep search means many requests. Splitting it by location or posting date keeps runs manageable.
  • Many domains. Each country site has its own layout and frequent A/B tests, so parsers need maintenance.
  • Terms of service. Indeed restricts automated access; see the legal section below.

Our Indeed scraper as an API

Our Indeed Jobs Scraper runs on Apify, so it behaves like the API Indeed no longer offers: send a JSON input, get structured jobs back. This input searches two keywords in two locations, keeping last week’s direct-employer, full-time postings:

{
  "keywords": ["data engineer", "analytics engineer"],
  "locations": ["Austin, TX", "Remote"],
  "country": "us",
  "rows": 200,
  "maxJobsPerSearch": 50,
  "datePosted": "7d",
  "jobType": "fulltime",
  "postedBy": "employer",
  "descriptionFormat": "plain"
}

The same run from Python, with the official apify-client package:

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run = client.actor("silentflow/indeed-jobs-scraper-ppr").call(
    run_input={
        "keywords": ["data engineer", "analytics engineer"],
        "locations": ["Austin, TX", "Remote"],
        "country": "us",
        "rows": 200,
        "maxJobsPerSearch": 50,
        "datePosted": "7d",
        "jobType": "fulltime",
        "postedBy": "employer",
        "descriptionFormat": "plain",
    }
)

for job in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(job.get("title"), job.get("companyName"), job.get("location"),
          job.get("salaryMin"), job.get("salaryMax"), job.get("jobUrl"))

Records also carry the posting date, salary currency and interval, categorized skills and, with scrapeCompany on, company industry, size and revenue. No Python? The same run is a single HTTP POST to https://api.apify.com/v2/acts/silentflow~indeed-jobs-scraper-ppr/run-sync-get-dataset-items with your token and the JSON above. For the full field list and workflow ideas, see our Indeed jobs scraper guide.

What it costs

Pay-per-result at $0.005 per job on Apify’s free plan, plus a negligible start fee per run and no subscription. 1,000 jobs come to about $5. A daily run collecting 500 new postings adds up to roughly 15,000 jobs a month, or about $75. Higher Apify plans pay slightly less per job, and Apify’s free credit covers a test run.

Need a job data feed, not a one-off export?

Most people looking for an Indeed API want a recurring feed: fresh listings for a job board, openings flowing into an ATS, or a labor-market dashboard that updates itself. That is what SilentFlow builds. We schedule extraction across Indeed and other job boards, deduplicate postings, normalize salaries and skills, deliver the results into your database, warehouse or ATS, and maintain the pipeline when the sites change. Tell us what you need.

  • Indeed’s terms prohibit it without permission. Indeed’s terms of service forbid using bots or scrapers to access or data-mine the site without its express written permission, and forbid using it to train third-party AI models. Scraping without that permission goes against those terms, and the responsibility sits with whoever runs the extraction. Keep volumes moderate and take legal advice before building a commercial product on the data.
  • Some fields are personal data. Contact emails in descriptions and CEO names and photos from company profiles identify people. For EU and UK listings GDPR applies, as does the CCPA in California: have a lawful basis, collect only the fields you use (scrapeCompany can be turned off), and set a retention period.
  • Analyze, don’t republish. Salary benchmarks, skill-demand tracking and hiring signals are internal uses. Copying listings wholesale onto your own job board reproduces employers’ and Indeed’s content, which the terms explicitly prohibit. If you show a job to anyone, link to the original posting.

Launch your scraping project

Need to automate data collection? Tell us what you need, we'll get back to you within 24 hours.

Send message