11 ATS Platforms with Public Job Posting APIs [2026]

A practical guide to the public ATS APIs that actually work for pulling jobs into a job board. Covers Greenhouse, Lever, Ashby, Workable, Recruitee, Personio, SmartRecruiters, Pinpoint, Gem, Polymer, and Teamtailor, with exact endpoints, undocumented feeds that also work, and what to do when an ATS has no public feed.

Abi Tyas TunggalJack Walsh
By Abi Tyas Tunggal and Jack Walsh· Updated on

If you are building a job board, relevant jobs are the product. Public ATS feeds are one practical way to retrieve published vacancies without private recruiting credentials. Some feeds still require employer configuration: Personio’s XML feed must be activated before it is available. Public access also differs from permission to redistribute listings; check the source’s terms or agreement.

This guide covers the public ATS sources that are actually useful for a job board, the exact endpoints they expose, and what to do when an ATS does not offer one.

What is an ATS, and what counts as a public job posting API?

An applicant tracking system (ATS) is the software employers use to publish roles, collect applications, and manage the hiring process. Greenhouse, Lever, Ashby, Workable, Recruitee, Personio, SmartRecruiters, Pinpoint, Gem, Polymer, and Teamtailor are all ATS platforms. If you want the broader distinction between ATS tools and job board software, start there.

For a job board, the part that matters is the public careers layer. A public job posting API is any documented endpoint or feed that lets you retrieve published jobs without asking each employer for API credentials first. In practice, that usually means one of two things:

  • a public JSON API
  • a public XML job feed

The useful fields are the same either way: title, location, description, department, employment type, updated date, source URL, and apply URL. That is enough to power a board, even if you still need to normalize titles, clean up locations, deduplicate listings, and expire jobs when they disappear from the source.

How job boards actually use public ATS APIs

Most job boards do not build a deep integration into each ATS. They pull the published jobs, store them in their own schema, add their own search and filtering, and then send candidates to the original apply URL.

The basic workflow looks like this:

  1. Fetch published jobs from the public ATS endpoint or feed.
  2. Normalize fields like location, workplace type, salary, department, and remote status.
  3. Deduplicate jobs by source URL, external job ID, or a combination of both.
  4. Re-sync on a schedule so new jobs appear quickly and closed jobs disappear.
  5. Display the jobs on your own board with your own search, filters, SEO pages, and monetization.

Keep the provider job ID, source board and original application URL. Expire missing records only after a complete, successful snapshot, including every required page; a failed request or partial response must not close existing jobs. Treat absent salary and location fields as unknown. On October 29, 2026, we confirmed every endpoint in this guide still returns jobs for a live employer. The example responses for Greenhouse, Lever, Ashby, Workable, Recruitee and Personio were captured on April 3, 2026; the others come from the October 29 test.

That is why public ATS APIs are valuable for job boards. They remove the hardest part of direct ATS work, which is authentication and customer-by-customer setup. They do not remove the rest of the operating work. You still need to handle freshness, deduplication, taxonomy cleanup, and source quality. If you want the broader picture, our guides on job feeds, job scraping, job wrapping, and job board aggregators cover the other ways boards get jobs onto the site.

11 ATS platforms with free public job posting APIs or feeds

These are the eleven options that each vendor describes in its own developer docs or help centre, linked in its section below. All eleven returned published jobs without employer credentials when we tested them on October 29, 2026.

PlatformPublic endpointFormatWhat you getMain limitation
GreenhouseGET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs?content=trueJSONPublished jobs, descriptions, departments, offices, apply URLs, updated timestampsNo native search or filtering
LeverGET https://api.lever.co/v0/postings/{site}?mode=jsonJSONPublished jobs, categories, hosted URLs, apply URLs, optional salary fieldsYou still need to build your own search layer
AshbyGET https://api.ashbyhq.com/posting-api/job-board/{job_board_name}?includeCompensation=trueJSONPublished jobs plus structured compensation summariesNo built-in search or filtering on the public feed
WorkableGET https://www.workable.com/api/accounts/{account_subdomain}?details=trueJSONPublished jobs plus job details from the public careers layerCompanion locations and departments come from separate endpoints
RecruiteeGET https://{company}.recruitee.com/api/offers/JSONPublished jobs, careers_url, careers_apply_url, department and tag filtersLighter metadata than Greenhouse or Ashby
PersonioGET https://{company}.jobs.personio.de/xml?language=enXMLPublished jobs, office, department, employment type, description blocksXML feed, not JSON
SmartRecruitersGET https://api.smartrecruiters.com/v1/companies/{companyIdentifier}/postingsJSONPublished jobs, structured location, employment type, release date; description and apply URL per postingFull description needs a second call per job
PinpointGET https://{company}.pinpointhq.com/postings.jsonJSONPublished jobs, HTML description, structured salary, workplace type, departmentNo posted date
GemGET https://api.gem.com/job_board/v0/{board}/job_posts/JSONPublished jobs, HTML and plain-text content, first-published and updated dates, departments, officesNo salary field
PolymerGET https://api.polymer.co/v1/hire/organizations/{slug}/jobsJSONPublished jobs, location, remote rules, published date, salary textDescription comes from a per-job call
TeamtailorGET https://{company}.teamtailor.com/jobs.rssRSSPublished jobs, description, publication date, remote status, locations, departmentRSS, 100 jobs per page by default

Greenhouse

Greenhouse is usually the easiest public ATS API to start with. The response includes the fields most job boards need: title, location, departments, offices, description content, updated timestamps, and apply URLs.

Replace acme with the company's Greenhouse board token.

Example live response from Stripe on April 3, 2026:

Lever

Lever is one of the better public JSON APIs if you want basic filtering at the source. It supports parameters like team, department, location, commitment, level, skip, and limit.

Replace lever with the company's Lever site name.

For an EU-hosted Lever board, use https://api.eu.lever.co/v0/postings/{site}?mode=json and the corresponding jobs.eu.lever.co career site. Find the site name in the employer’s career URL. Follow skip and limit pagination rather than treating the first 20 results as a complete snapshot. See the official Lever Postings API.

Example live response from Dun & Bradstreet on April 3, 2026:

Ashby

Ashby is the public ATS feed with the cleanest compensation support. If salary matters on your board, includeCompensation=true is the parameter to care about.

Replace ashby with the company's Ashby job board name.

Before adding Ashby records to search or category listings, exclude records with isListed: false: those are intended for direct-link access only. Preserve jobUrl, applyUrl and geographic eligibility separately from isRemote. See the Ashby public API contract.

Example live response from Ashby on April 3, 2026:

Workable

Workable's public careers layer is split across a few endpoints. The main one returns the public account and job data, and the companion endpoints return locations and departments.

Replace acme with the employer's Workable account subdomain.

Example live response from Epignosis on April 3, 2026:

Recruitee

Recruitee exposes a public offers endpoint on each employer subdomain. It is simple to call and works well when you just want published jobs plus the public careers and apply URLs.

Replace acme with the employer's Recruitee subdomain.

Example live response from Adamsmithinternational1 on April 3, 2026:

Personio

Personio is the main XML-based public source worth knowing about. If your import pipeline already supports XML, it is straightforward to add.

Replace acme with the employer's Personio career-site subdomain. Some accounts use .com instead of .de, so check the live career-site hostname before hardcoding it.

Example live response from Personio on April 3, 2026:

SmartRecruiters

SmartRecruiters' Posting API serves every job an employer has made public on its SmartRecruiters career site. The list endpoint returns titles, structured locations, employment type and release dates, paginated with limit and offset.

Replace acme with the company identifier from the employer's SmartRecruiters career URL. For the description, apply URL and job ad sections, fetch each posting's ref URL.

The Posting API docs say it supports API key and OAuth 2.0 authentication; credentials matter for internal postings. Public postings answered our calls without a key, but if you plan to rely on this source at volume, check the current terms with SmartRecruiters.

Example live response from Grab on October 29, 2026:

Pinpoint

Pinpoint publishes a JSON endpoint on every career site, and it has the richest salary data of any feed in this guide: minimum, maximum, currency, frequency, and whether the employer chose to show it.

Replace acme with the employer's Pinpoint subdomain. The Pinpoint jobs JSON docs describe filters such as department and location, and note that postings.json replaces the older jobs.json. Respect compensation_visible: if it is false, keep the salary off your board.

Example live response from Stratom on October 29, 2026:

Gem

Gem's Job Board API will look familiar if you already support Greenhouse: the response shape is close, with content in both HTML and plain text, plus first-published and updated timestamps.

Replace acme with the employer's Gem job board path, the part after jobs.gem.com/ in their careers URL. See Gem's Job Board API guide.

Example live response from Dragonfly on October 29, 2026:

Polymer

Polymer documents its Public API as unauthenticated and intended for job board integrations. The list endpoint is paginated (meta.next_page) and carries remote-work rules, such as required countries of residency, that most feeds leave out.

Replace acme with the employer's Polymer slug, from jobs.polymer.co/{slug}. The list omits the description; fetch each job by ID to get it. The Polymer developer docs note that requests are rate-limited, so back off on a 429 response.

Example live response from Fleet Robotics on October 29, 2026:

Teamtailor

Teamtailor career sites publish an RSS feed of open jobs. The Teamtailor RSS guide states that everything in it is publicly available: title, description, publication date, job URL, remote status, a global ID, locations, department and role.

Replace acme with the employer's Teamtailor subdomain, or use their custom careers domain followed by /jobs.rss. The feed returns 100 jobs by default; use per_page and offset to page through larger employers.

Example live response from Robot.com on October 29, 2026:

Teamtailor also has a JSON API with a "public" key scope, but the employer has to create that key and share it with you.

Undocumented endpoints that also work

Five more ATS platforms serve published jobs as JSON without credentials, but none of their vendors document these endpoints for this use. They are the same requests the vendor's own career pages make in the browser. All five returned live jobs on October 29, 2026. Use them knowing they can change or disappear without notice, and keep a fallback such as job wrapping for employers that matter to your board.

PlatformEndpointWhat you getWatch out for
Breezy HRGET https://{company}.breezy.hr/jsonTitle, URL, published date, employment type, location, salary textNo description in the list
BambooHRGET https://{company}.bamboohr.com/careers/listTitle, department, location, remote flagDescription and pay need /careers/{id}/detail per job
RipplingGET https://api.rippling.com/platform/api/ats/v1/board/{slug}/jobsTitle, department, location, job URLThin list; no description or dates
WorkdayPOST https://{tenant}.wd{N}.myworkdayjobs.com/wday/cxs/{tenant}/{site}/jobsTitle, location text, relative posted date, job pathNeeds a JSON body with limit (20 at most) and offset; relative dates such as "Posted Today"; behaviour varies by tenant
ManatalGET https://www.careers-page.com/api/v1.0/c/{slug}/jobs/Title, description, location, salary visibility; paginatedRate-limited: answers 429 if you call too fast

Workday is the one most job boards ask about, because so many large employers use it. The request needs the tenant, the data-centre number (wd1, wd5 and so on) and the career site name, all visible in the employer's careers URL:

Page with offset: Workday rejects a limit above 20 with a 400.

Example live response from Globus Medical on October 29, 2026:

ATS platforms without an open feed

Many ATS platforms do have job APIs, but they need a token or key from the employer, or they are reserved for approved partners. You can still use them when an employer agrees to share access, but you cannot build coverage from them on your own.

PlatformWhat existsWhat you need
ComeetCareers API (/careers-api/2.0/company/{uid}/positions)A company token from the employer
JOINJobs API v2The employer's API token
Teamtailor (JSON)JSON API with a public key scopeA key the employer creates
JazzHRAccount APIThe employer's API key
Zoho RecruitREST APIOAuth 2.0 credentials
DoverJobs APIThe employer's API key
HomerunDeveloper API, plus job XML feedsAn API key from the employer, or a feed link they generate
iCIMSStandard XML feed for job boardsApproval from iCIMS and OAuth 2.0

For these, career-page extraction is usually the practical route, or a platform that already sources from them.

What to do when an ATS does not have a public API

Most boards do not live on public ATS APIs alone. Once you move beyond the sources above, you usually combine four different methods:

  • public ATS APIs like Greenhouse, Lever, or Ashby
  • public XML feeds like Personio or feed-based Recruitee setups
  • career-page extraction through job wrapping or job scraping
  • pre-built job data sources and job feeds

That is also the point where most operators should stop asking, "Can we integrate one more ATS ourselves?" and start asking, "Do we really want to own this pipeline?"

If your actual goal is to get relevant jobs onto your board, keep them fresh, deduplicate them, and get them indexed, Cavuno is the simpler path. Cavuno already pulls from public ATS APIs, career pages, feeds, and other public job sources, then handles the parts most teams underestimate:

  • deduplication by source URL
  • expiry when jobs disappear
  • company enrichment
  • search-ready normalization
  • moderated imports when you want editorial control

That is what Backfill is for. You define the kinds of jobs you want, Cavuno imports matching jobs onto the board, and you can review them through job moderation if you want tighter control. Once they are live, you can run the board on your own custom domain and speed up discovery with the Google Indexing API.

If you are building an HR tech product whose value is the integration itself, direct ATS work makes sense. If you are building a job board, the better question is usually how to get reliable job supply without turning source maintenance into your product.

Which public ATS API is best for a job board?

The better question is not which API is "best" in the abstract. It is which ATSs show up in the kinds of companies your board cares about.

  • Greenhouse is the highest-leverage place to start for startup, software, and venture-backed company coverage. If your board targets tech, product, engineering, or venture-backed hiring, Greenhouse will show up constantly.
  • Lever is common in tech as well, especially among growth-stage companies and teams that want a polished hosted careers experience. It is a good second source after Greenhouse for startup-heavy niches.
  • Ashby tends to show up in newer, high-growth startups, especially companies that care about modern recruiting workflows and salary transparency. If your niche overlaps with startup hiring or tech-forward employers, it is worth supporting.
  • Workable appears much more often outside the classic venture-backed startup world. It is common among SMBs, agencies, and operational teams that want an easy careers setup without a heavyweight recruiting stack.
  • Recruitee is common among SMB and mid-market teams, particularly in Europe. If your board skews toward smaller employers or international hiring outside the US venture ecosystem, it is a useful source.
  • Personio matters most when your target employers are in Europe, especially DACH markets. It is less about broad global coverage and more about reaching the companies that already run hiring through Personio.
  • SmartRecruiters is common among large and enterprise employers worldwide, so it adds volume that the startup-focused feeds miss.
  • Pinpoint is the best source when salary data matters: it is structured, and it tells you whether the employer wants it shown.
  • Gem and Polymer show up mostly among startups and venture-backed companies. If you already support Greenhouse, Gem is the quickest one to add.
  • Teamtailor is widespread among European employers, particularly in the Nordics. Its RSS feed is easy to add if your pipeline already reads XML.

For most operators, that is enough to prove the concept quickly. After that, the problem stops being "which public ATS has an API?" and becomes "how do we keep jobs clean, current, and useful at scale?" That is the part that determines whether a board feels empty and stale or alive and worth returning to.

Frequently asked questions

Related posts

Cover Image for What Is a Job Board Aggregator? How to Build One in 2026 (Without Code)
Technology·

What Is a Job Board Aggregator? How to Build One in 2026 (Without Code)

Learn what a job board aggregator is, how it works, and how to build one step-by-step. Covers AI-powered job processing, monetization strategies, and platform comparison.

Cover Image for Job Feeds for Job Boards: How to Backfill, Manage, and Monetize in 2026
Technology·

Job Feeds for Job Boards: How to Backfill, Manage, and Monetize in 2026

Learn how to source, manage, and monetize job feeds for your job board. Covers backfilling strategy, feed providers, quality control frameworks, AI-powered feed management, and real revenue math.

Cover Image for Job Wrapping Explained: How It Works, When It Fails, and How to Do It Right
Technology·

Job Wrapping Explained: How It Works, When It Fails, and How to Do It Right

Learn what job wrapping is, how it works technically, common implementation problems that damage candidate trust, Google for Jobs compliance requirements, and quality controls that separate successful...

Cover Image for How to add a job board to your community
Getting Started·

How to add a job board to your community

Add a job board to Circle, Skool, Mighty Networks, Slack, or Discord. Choose a link, widget, or SDK page, with launch copy and posting rules.

Cover Image for How to add a paid job board to your newsletter
Getting Started·

How to add a paid job board to your newsletter

Add a paid job board to your newsletter with Substack, beehiiv, Ghost, Kit, or Mailchimp. Compare setup options, pricing, and launch templates.

Cover Image for How to create an association job board: A practical launch guide
Associations·

How to create an association job board: A practical launch guide

Plan, price, launch, and operate an association job board with a staff ownership map, member-pricing example, transparent budget, and launch checklist.