If you are building a job board or careers page and need to automate job imports, one of the most reliable data sources is the Applicant Tracking System (ATS) your clients already use.
Several ATS platforms expose a public job posting API that does not require authentication. You can call these endpoints to retrieve all published jobs for a given client and keep your job board or career page in sync without scraping HTML or manual uploads.
In this guide we cover 9 ATS platforms with public job posting APIs, their exact endpoints, and what to consider when integrating directly or via an aggregator like TheirStack.
How public ATS job posting APIs usually work
Most ATS systems follow a similar pattern for their public job posting APIs:
- Public job board endpoint: A URL that lists all published jobs for a given company or job board.
- JSON response: Structured fields like title, location, department, employment type, and sometimes compensation.
- Limited parameters: Basic filtering or pagination, but not the full query power of their authenticated API.
- Read-only access: Designed to power job boards and career pages, not to update or manage candidates.
These endpoints are usually safe to call from a backend service or scheduled job that syncs postings into your own database, where you can enrich, filter, and route them as needed.
1. Ashby
Ashby has a simple public API that allows anyone to retrieve jobs from Ashby clients. To retrieve jobs, use:
curl "https://api.ashbyhq.com/posting-api/job-board/{clientname}?includeCompensation=true"The API returns JSON with most relevant job posting fields. Filtering or searching is not possible with this endpoint. More advanced endpoints are available for Ashby customers via the Ashby Developer API.
2. Greenhouse
Greenhouse has a simple public API that allows anyone to retrieve jobs from Greenhouse clients. To retrieve jobs, use:
curl "https://api.greenhouse.io/v1/boards/{clientname}/jobs?content=true"The API returns JSON with most relevant job posting fields. Filtering or searching is not possible with this endpoint. More advanced endpoints are available for Greenhouse customers via the Greenhouse Harvest API.
3. Lever.co
Every Lever.co customer has a public API that allows you to retrieve jobs. No authentication is required. To retrieve jobs, use:
curl "https://api.lever.co/v0/postings/{clientname}"The base URL is https://api.lever.co. The result is JSON or HTML with all relevant job posting fields. No further filtering is possible, except selecting a single job by appending the job ID to the end of the GET request.
4. Recruitee
Recruitee has a simple public API that allows anyone to retrieve jobs from Recruitee clients. To retrieve jobs, use:
curl "https://{clientname}.recruitee.com/api/offers"The API returns JSON with most relevant job posting fields. Filtering or searching is not possible with this endpoint. More advanced endpoints are available for Recruitee customers via the Recruitee ATS API.
5. Workable
Workable has a simple public API that allows anyone to retrieve jobs from Workable clients. To retrieve jobs, use:
curl "https://apply.workable.com/api/v1/widget/accounts/{clientname}"The API returns JSON with most relevant job posting fields. Filtering or searching is not possible with this endpoint. More advanced endpoints are available for Workable customers on v3 of the API.
6. SmartRecruiters
SmartRecruiters exposes a public JSON endpoint per company.
curl "https://api.smartrecruiters.com/v1/companies/{clientname}/postings"7. HireHive
HireHive provides a public jobs API per company subdomain. To retrieve jobs, use:
curl "https://{companyname}.hirehive.com/api/v1/jobs"The API returns JSON and supports pagination plus optional filters (such as country or category filtering). You can also paginate explicitly, for example:
curl "https://{companyname}.hirehive.com/api/v1/jobs?page=1"8. Manatal (Career Page API)
Manatal exposes a public Career Page API endpoint that returns published job posts and supports both search and multiple filters. To retrieve jobs, use:
curl "https://api.careers-page.com/open/v1/career-pages/{client_slug}/job-posts"The API returns JSON with published job postings for the specified client slug and lets you refine results with query parameters for searching and filtering.
9. Breezy HR
Breezy HR exposes a simple public endpoint per company that returns open roles from their hosted job board. To retrieve jobs, use:
curl "https://{company}.breezy.hr/json"The endpoint returns clean JSON that is easy to consume and is especially common among smaller and early-stage startups. Filtering is limited, so you typically fetch all jobs for a company and then filter or map them on your side.
10. Remotive
Remotive is a remote job board that exposes a simple public API to search remote jobs across many companies and categories.
curl "https://remotive.com/api/remote-jobs?search={clientname}"The API returns JSON with job postings that match the search query, including fields like job title, company name, job type, and location.
11. Jobicy
Jobicy is another remote job board that exposes a public API to search remote jobs by industry and then filter by company on your side. For example, to fetch up to 10 remote jobs for a given industry and only keep those from a specific company:
curl -s "https://jobicy.com/api/v2/remote-jobs?count=10&industry=<industry>" \
| jq '.jobs[] | select(.companyName=="<company>")'This pattern lets you use Jobicy as a broad source of remote roles while narrowing down results to companies that are actively hiring for the industries you care about.
12. Arbeitnow
Arbeitnow provides a free public job board API that you can filter for roles offering visa sponsorship. To retrieve the latest jobs that explicitly support visa sponsorship:
curl "https://www.arbeitnow.com/api/job-board-api?visa_sponsorship=true"The API returns JSON with job postings and supports pagination via the page query parameter (for example, ?visa_sponsorship=true&page=2). This is useful if you want to focus your job board or outreach workflows on companies that are open to sponsoring visas.
13. Rise
Rise exposes a public jobs API focused on curated tech and startup roles. To retrieve the most recent jobs:
curl "https://api.joinrise.io/api/v1/jobs/public?page=1&limit=20&sort=desc&sortedBy=createdAt&jobLoc="The API returns JSON with a jobs array and metadata like count, and you can filter by location using the jobLoc query parameter (for example, jobLoc=San%20Francisco). Per their API terms, you must link back to the corresponding job URL on Rise and credit Rise as the source when you display these jobs.
How to get job postings in practice
Once you know the endpoints, you still need to discover which clients (board names, subdomains, account slugs) to call. You can do that manually and then poll each endpoint, or use an aggregator.
Manual approach: discovering and polling client IDs
Public ATS APIs do not list their clients. You have to discover client IDs yourself. One way is to use Google site search so that results are limited to that ATS’s job pages. For Ashby, for example, you can search for pages under their job board domain:
Search Ashby job boards on Google
From the result URLs you can extract the client IDs (the path or subdomain that identifies each company). The same idea works for other ATS: use site: on their job board domain and derive the client identifier from the URLs.
Example client IDs you can use for testing (e.g. with Ashby): ashby, vault. Replace {clientname} in the endpoint with one of these to try the API.
Then call the endpoint once per client. For example, for Ashby:
curl "https://api.ashbyhq.com/posting-api/job-board/ashby?includeCompensation=true"You must run this (or the equivalent for Greenhouse, Lever, Recruitee, Workable,...) for every client you care about. To keep data fresh, you typically schedule these calls on a cadence (e.g. every few hours or daily). The more clients and ATS you support, the more requests and maintenance you have.
Using an aggregator: one API, many sources
With TheirStack you can query jobs from 300k+ career sites and ATS in one place. You can pull from all sources or narrow by source (e.g. only Ashby). No need to discover or maintain client IDs per ATS; you get a single, consistent API and filter by source when you want a specific ATS.
Direct ATS APIs vs. aggregated job data
Integrating directly with each ATS can make sense if:
- You only support a small, known set of ATS platforms.
- Your customers are willing to help you configure each integration.
- You want full control over the exact fields and mapping.
However, as soon as you want broad coverage across many ATS, job boards, and career pages, maintaining dozens of connectors becomes expensive. This is where job data aggregators like TheirStack can help by:
- Normalizing jobs across ATS, job boards, and custom career sites.
- Deduplicating the same role posted to multiple sources.
- Providing consistent company data (firmographics, technographics, and more).
- Giving you one API to power your job board, product, or outbound workflows.
If you are evaluating whether to build and maintain many ATS integrations yourself or plug into a single job data API, it is often cheaper and faster to start with an aggregator and then add custom ATS integrations only where you truly need them.
Choosing the right approach for your project
To decide how to work with ATS job posting APIs, start by listing:
- Which ATS your current or target customers actually use.
- How often you need data refreshed (near real-time vs. daily).
- Whether you need deep ATS objects (candidates, interviews) or just job postings.
- How much engineering time you can realistically invest in integrations and maintenance.
If you mainly care about complete, fresh job postings across many sources, aggregators like TheirStack significantly reduce integration overhead while still letting you respect your customers' existing ATS workflows.
For a small number of high-value customers, layering a direct integration with a specific ATS on top of the aggregator can give you the best of both worlds: broad coverage plus deep control where it matters most.