A job API is a programmatic interface that returns job postings - title, company, location, description and often more - as structured data you can query from your own code. Job boards use it to fill their listings, analysts use it to measure hiring demand, and product teams use it to feed recruiting tools or machine learning models.
This guide explains what job APIs are, which kinds exist, how to evaluate one before you commit, and how to actually pull job posting data through an API. If you already know what you need and just want an API key, go straight to Techmap's Job Posting API - it has a free tier and covers 250 countries & territories.
What is a job API?
An API (Application Programming Interface) is a contract between two systems: you send a request in a defined format, the provider sends back data in a defined format. A job API applies this to job postings.
A typical request looks like "give me all software engineering jobs in Germany created last week, excluding duplicates". The response is a list of job objects, usually in JSON, each with fields such as:
- Core fields: job title, company name, location (city, state, country), posting date, description, apply URL
- Classification: industry, occupation, department, contract type (permanent, freelance, internship ...), work place (remote, hybrid, onsite)
- Enrichment: extracted skills, salary (where stated), geo-coordinates, timezone, career level
- Provenance: the source portal, the original URL, duplicate flags, an expiry or "active until" date
You authenticate with an API key, filter with query parameters, and page through results. The provider handles the hard part: finding, scraping or receiving the postings, normalizing messy free text into consistent fields, and keeping everything up to date.
Why not just scrape job sites yourself?
You can, and for a single site it is often a weekend project. The cost shows up later. Every source has its own HTML, its own anti-bot measures and its own way of writing locations and dates. Sites change their layout without notice, so scrapers break regularly. Once you go beyond a handful of sources you are maintaining infrastructure, proxies, parsers and a deduplication pipeline instead of building your product.
A job API moves that work to a provider who does it for many customers at once. You trade some control (you only get the sources and fields the provider offers) for predictable cost and much less maintenance.
The three kinds of job APIs
"Job API" is used for quite different things. Knowing which one you are looking at saves a lot of time.
| Type | What it does | Data scope | Typical users |
|---|---|---|---|
| Job search API | Lets end users search jobs, often powered by one aggregator's index; results may be sponsored or ranked for clicks | One provider's listings, often only current postings | Apps and sites that show jobs to job seekers |
| Job board API | The API of a single job board or ATS; used to post jobs to it or read its own listings | One board or one employer's career site | Employers, recruiters, ATS integrations |
| Job data API | Aggregates postings from many sources, normalizes and deduplicates them, exposes them for any use | Many sources and countries, often with history | Job boards (backfill), analysts, HR tech, data science |
A few practical consequences:
- Job board APIs are narrow. Many large boards no longer offer an open API for reading listings at all, or restrict it to partners. Where they do, you only get that one board.
- Job search APIs are built for display. Some return only snippets and require you to send users back to the original site, which works for a search widget but not for analytics.
- Job data APIs are built for reuse. They usually return the full description, add enrichment fields and come with licensing that allows storage and analysis. Techmap's Job Posting API belongs in this category.
There is also a delivery dimension: some providers offer the same data as a REST API, as an RSS feed for job board importers (see our RSS feed API), or as bulk files. More on that below.
What people use job APIs for
The use cases fall into a few groups:
- Backfilling job boards. Niche or regional boards rarely get enough direct postings to look alive. Pulling relevant postings for their category or region through an API fills empty search results and gives job seekers a reason to return.
- Labor market and hiring trend analysis. Counting postings by country, occupation or skill over time shows where demand grows or shrinks - useful for market entry decisions, workforce planning and research.
- Sales intelligence and lead generation. A company that hires five data engineers is likely investing in data infrastructure. Postings reveal growth, new locations and the tools a company uses, which makes them a source of buying signals.
- Competitor monitoring. Hiring patterns of competitors hint at new teams, products or markets before they are announced.
- Recruiting and HR tech products. Salary benchmarking, skill gap analysis or job recommendation features all need a steady stream of postings.
- Data science and ML. Job descriptions are a large, naturally labeled text corpus for classification, entity extraction (skills, titles) and matching models.
How to evaluate a job API: a practical checklist
Headline numbers say little. Test a provider against your actual needs - here is the checklist we would use ourselves.
1. Coverage by country and source
- Which countries are covered, and how many postings per month do you get in the countries you care about? A large global number says little about your market.
- Which source types are included: company career pages and ATS platforms, job boards, aggregators, public employment offices? Career pages tend to be the most original source; aggregators add reach but also duplicates.
- Is the source list published? A provider that names its sources (like our list of job portals) makes it easier to check for gaps.
How to test: run count queries for your top countries, occupations and a few employers you know are hiring, and compare against what you see on their career pages.
2. Freshness and update frequency
- How long after a job goes live is it searchable through the API - minutes, hours or a day?
- Is the index updated continuously or by a nightly batch?
- Are expired postings marked or removed? Look for a validity or "active until" field.
How to test: pick a few postings published today on known career pages and check when they show up. Query by creation date for the last 24 hours and look at the volume.
3. Deduplication
The same job is often posted on the company site, two job boards and an aggregator. Without deduplication your counts are inflated and your job board shows the same job four times.
- Does the provider deduplicate, or at least flag duplicates?
- What is the rule (for example same company, title and location within a few days)?
- Can you filter duplicates out in the query?
4. Fields, normalization and enrichment
- Are locations normalized to countries and cities, or left as free text?
- Is the full description included, and in which format (HTML, Markdown, plain text)?
- Which enrichment fields exist: industry, occupation, skills, salary, remote/hybrid, contract type, geo-coordinates?
- How well populated are they? A salary field that is empty in most records is not a salary feature. Ask for fill rates or measure them on a sample.
5. Historical data
- How far back does the API go? Many APIs only cover current or recent postings.
- Is a longer archive available separately, and in which form?
- For trend analysis you typically need at least a couple of years of consistent data.
6. Delivery formats and access patterns
- Response formats: JSON is standard; CSV, XML, RSS or Parquet help depending on your stack.
- Pagination: page-based is simple, cursor-based is necessary for large result sets.
- Is there a count or statistics endpoint for analytics without downloading every record?
- For large volumes, is there a bulk alternative (files delivered to cloud storage) so you don't page through millions of records via HTTP?
7. Pricing model
Common models are per request, per record, monthly subscription tiers with quotas, per country, or custom enterprise contracts. Check:
- What happens at the quota limit - hard block or overage billing?
- Is there a free tier or sample to test with real data?
- Does the price scale with the number of records you need, not with features you don't use?
8. Terms and licensing
This one is skipped surprisingly often.
- May you store the data, and for how long?
- May you display postings publicly on your job board, or only analyze them internally?
- May you use the data to train ML models or resell derived products?
- Do you have to link back to the original source?
A cheap API with a license that forbids your actual use case is not cheap.
How to access job posting data through an API
The concrete steps are similar for most providers. Here is how it works with Techmap's Job Posting API, which is hosted on RapidAPI.
- Create an account and subscribe. Sign up on RapidAPI and subscribe to the free Basic plan of the Job Postings API (no credit card required). It includes 100 requests, i.e. 1,000 job postings, per month.
- Copy your API key. Send it in the
X-RapidAPI-Keyheader of each request, or as therapidapi-keyURL parameter. - Make a first request. Filter by country, creation date and any other field:
curl -X GET \
"https://daily-international-job-postings.p.rapidapi.com/api/v2/jobs/search?countryCode=de&workPlace=remote&dateCreated=$(date +%Y-%m)&isDuplicate=false&page=1" \
-H "X-RapidAPI-Key: YOUR_API_KEY"
- Read the response. You get a metadata envelope with
totalCountand aresultarray of up to 10 postings per page. Each job includes normalized fields (title, company, city, country, industry, skills, work place ...) and ajsonLDobject that is a valid schema.org JobPosting with the full description. - Paginate and sync. Use
pagefor smaller result sets and cursor-based pagination for larger ones. For a job board, a daily job that fetches yesterday's postings for your categories is usually enough. - Use counts for analytics. The
/countendpoint returns the number of matching postings without returning job data, which is the cheap way to build time series by country, industry or skill.
Always set dateCreated (or a date range) explicitly - without it the API defaults to a recent date. The full parameter list is in the Job API overview, and working code in Python and JavaScript is on the developer page. For a longer walkthrough see our step-by-step integration tutorial and, if you are new to APIs in general, getting started with APIs in JavaScript.
API, data feed or dataset?
An API is not always the right delivery mechanism. A rough rule:
| Need | Best fit |
|---|---|
| Query specific slices, build a search or backfill a board, moderate volumes | API - e.g. Job Posting API |
| Mirror all postings of one or more countries into your own warehouse, continuously | Bulk data feed - e.g. job data feeds as files on AWS |
| Analyze trends over several years, train models on a large corpus | Historical dataset - e.g. job datasets, one-time purchase |
| Import into a hosted job board system that reads feeds | RSS feed - e.g. the RSS API |
Many teams combine them: a historical dataset to build the model or baseline, then the API or a feed to keep it current. Our post on job posting data in JSON, CSV, RSS and more covers the format side in more detail.
Try it: Techmap's Job Posting API
If you want to test the checklist above against real data, the Job Posting API is the quickest way to start:
- Job postings from 200+ sources - career pages, job boards, aggregators and employment offices - in 250 countries & territories (including "Remote")
- About 8M new job postings per month; new postings are typically searchable within minutes
- Duplicates flagged and filterable, normalized locations, enrichment such as industry, occupation, skills and work place
- JSON by default, also CSV, RSS, ATOM, XML and Parquet
- Free Basic plan with 1,000 job postings per month; paid plans from $29/month at about $1 per 1,000 job postings
The API covers the last 3 months. For older data, the historical job datasets go back to January 2020 (451M+ job postings since then).
FAQ
What is a job API in simple terms?
A job API is a service you call from your code to get job postings as structured data instead of reading them on websites. You send filters such as country, job title or date, and receive a list of matching jobs with consistent fields.
How do I access job posting data through an API?
Pick a provider, sign up and get an API key, then send HTTP requests with your filters and parse the JSON response. With Techmap you subscribe to the free Basic plan on RapidAPI, put the key in the X-RapidAPI-Key header and call the /api/v2/jobs/search endpoint with parameters like countryCode and dateCreated. Details and code examples are on the developer page.
What is the difference between a job search API, a job board API and a job data API?
A job search API powers job search for end users and is usually limited to one aggregator's current listings. A job board API belongs to a single board or ATS and is mainly for posting jobs or reading that board's own listings. A job data API aggregates and normalizes postings from many sources for reuse in job boards, analytics and ML, often with broader licensing.
How do I evaluate coverage and freshness of a job postings API?
Test with your own queries rather than relying on headline numbers. For coverage, count postings in your target countries, occupations and for employers you know, and compare with their career pages. For freshness, check how quickly postings published today appear, whether the index updates continuously or in batches, and whether expired jobs are marked. A free tier makes this possible before you pay.
Do job APIs include historical data?
Often only partially. Many job APIs focus on current or recent postings, because their main use is display and backfill. Historical archives are usually sold separately as datasets. Techmap's API covers the last 3 months; historical datasets with postings since January 2020 are available per country as a one-time purchase.
What does a job API cost?
It varies widely: some job board APIs are free for partners but limited to one site, aggregated data APIs typically charge per request or per record with monthly tiers, and enterprise contracts can run much higher depending on volume and license. Check overage rules and licensing, not just the entry price. Techmap's Job Posting API has a free tier with 1,000 postings per month and paid plans from $29/month - about $1 per 1,000 job postings. Bulk data feeds cost from $9 per country and month, depending on the country's posting volume; see pricing for all options.
Can I use job API data on my own job board?
That depends entirely on the provider's license. Some APIs only allow linking to the original posting, others allow storing and displaying the full posting. Check the terms before you build. Techmap's data is formatted along Google's JobPosting structured data so it can be listed directly on job boards.
How often should I sync data from a job API?
For a job board, a daily sync of the previous day's postings is a sensible default; high-traffic boards may poll more often. For analytics, monthly or weekly pulls via count endpoints are usually enough. Remember to also remove or hide postings that have expired.