05Jobs API
The Jobs API — search listings by title and place, with the salary fill rate on every row
Give it a job title and a place, and the Jobs API returns structured listings ready to work — title, company, location, a direct link to apply. This page explains what it returns, how it gets past the 1,000-result wall that stops most job scrapers, and how it shows you the salary fill rate before you spend a cent.
By job title and a country, region or city
Full description, seniority, applicant count
Past the 1,000-position cap, city by city
What the Jobs API returns
One row per listing, deduplicated on the source's own identifier. Every row carries the fields the source always publishes:
- title, company, location — the location parsed into city, region and country, with no extra request.
- url — a direct link to apply.
- published — the posting date, when the source dates the card.
- salary — as published, or
null. Never invented.
Turn on the full fiche and each row also gets the full description, seniority, employment type, job function, industry, and applicant count — one extra request per listing, so you pay for depth only when you ask for it.
Getting past the 1,000-result wall
The source hard-stops at 1,000 positions per query. Beyond that, it serves nothing at all. Most scrapers hit that ceiling silently; this one is built to segment around it:
- Add cities in Villes supplémentaires — each one is a fresh 1,000-position budget.
- Turn on the three publish-date windows (24 h / 7 d / 30 d) to split the same search by recency, ×3 the reachable listings.
Measured on one search: 929 listings on a single France query → 2,727 with the three windows → 5,028 with eight cities.
What it costs — the short version
Billed per result, in two tiers: a plain listing row and a row with both a published salary and a direct link. The full per-1,000 breakdown, and how it compares to a hosted jobs-data provider, is on the pricing page.
The fill rate, before you pay
Salary is the field everyone wants and few listings publish. Rather than let you find that out after the run, every batch reports the real fill rate of each field. A real software-engineer sweep:
Nine percent on salary is the honest answer for this search — read from the
batchCompleteness block, not from a support ticket after billing.
What a row looks like
GET /rechercher?metier=software+engineer&lieu=United+States
{
"count": 300,
"completeness": { "title": 100, "company": 99, "location": 100, "salary": 9, "url": 100 },
"jobs": [
{
"title": "Full-Stack Developer",
"company": "Example Inc",
"location": "Austin, Texas, United States",
"city": "Austin",
"region": "Texas",
"country": "United States",
"published": "2026-08-10",
"salary": null,
"url": "https://www.linkedin.com/jobs/view/4446697394"
}
]
}Questions
What is a Jobs API?
A Jobs API is an HTTP service that returns structured job listings — title, company, location, a direct link to apply, and where published, salary and applicant count — from a job title and a place. Instead of scraping a job board page by page, you send a query and get clean rows back, ready to store and filter.
Is there an official Indeed API or LinkedIn Jobs API?
Public, self-serve job-listing APIs from Indeed and LinkedIn are heavily restricted or closed to most developers, which is why teams turn to a collection API. RankFabrik's Jobs API reads the public, logged-out job-listing channel — no account, no session, no protection bypassed — and returns the same fields you would read on the page.
How do I get more than 1,000 job listings for one search?
The source hard-stops at 1,000 positions per query — beyond that it serves nothing. The Jobs API works around it for you: segment the search by extra cities, or sweep the three publish-date windows (24 h / 7 d / 30 d), and each segment re-opens a fresh 1,000-position budget. Measured on one search: 929 listings on a single query rose to 2,727 with the windows added and 5,028 with eight cities.
Which fields come back on every job listing?
Title, company, location (parsed into city, region and country), a direct link, and the publication date when the source dates the card. With the full-fiche option on, each row also carries the full description, seniority, employment type, job function, industry and applicant count. Salary is returned when published — often it is not, and the completeness block tells you the real rate for your search.
Why is salary missing on so many listings?
Most job cards simply do not publish a salary — that is a property of the source, not the API. Nothing is invented to fill the gap: an unpublished salary comes back as null, and batchCompleteness.salary reports the exact share of rows that carried one, so you know before you commit volume.