jobs api · commercial use
Millions of open jobs, one API, one flat price.
Postings read straight from employers’ own applicant-tracking systems, de-duplicated, classified and linked to the company behind them. Use them in your product under a plain licence — no per-job metering, no sales call.
The same API answers without a key for personal and non-commercial use, so you can build against it today and add a key when you ship.
- open postings, de-duplicated
- 5.3K
- companies with profiles
- 58
- ATS platforms read directly
- 158
- requests a minute on Data
- 6,000
who it is for
Built for products that show jobs to people.
Job boards
Fill a niche board by country, category or stack, and keep it current without running a crawler fleet of your own.
Recruiting and HR tools
Show live openings beside candidates, track which companies are hiring for what, and link straight to the employer’s own ATS.
AI agents and assistants
Give a product’s agent a real catalogue to search — structured filters, full descriptions in Markdown, no scraping.
Market research
Count demand by skill, seniority, region or work mode, from postings read at the source rather than reposted.
what you get
A posting, already structured.
Every field on every plan, and every filter the site’s own search has — country, region, city, category, seniority, skills, work mode, salary, company, source and freshness.
- Role
- title, category, seniority, employment type, skills
- Place
- countries, regions, cities, work mode (remote / hybrid / on-site)
- Pay
- salary range, currency and period when the posting states it
- Company
- name, slug, industry, size, headquarters, founding year, YC batch
- Apply
- the employer’s own ATS link and the source platform it came from
- Lifecycle
- posted, first and last seen, and closed — a closed posting says so
curl "https://freehire.me/api/v1/jobs/search?countries=de&category=software_engineering&limit=100" \ -H "Authorization: Bearer $FREEHIRE_API_KEY"
{
"data": [{
"public_slug": "golang-software-engineer-…-ebn6r4wq",
"title": "Golang Software Engineer - Identity & Access Management",
"company": "Allianz",
"company_slug": "allianz",
"source": "successfactors",
"url": "https://internal-careers.allianz.com/job/…",
"countries": ["de", "pt"],
"cities": ["Berlin", "Lisbon"],
"skills": ["go", "keycloak", "oauth", "rbac", "sso"],
"enrichment": { "category": "software_engineering", "employment_type": "full_time" },
"posted_at": "2026-10-17T00:00:00Z",
"closed_at": null
}],
"meta": { "total": 161, "limit": 100, "offset": 0 }
}how it is priced
You pay for the rate, not for the rows.
Metered by record
The usual job-data pricing: a monthly allowance of records, and every posting you read spends it. Around $100 a month buys tens of thousands of postings; mirroring a catalogue of millions runs to thousands.
Flat on freehire
One monthly price and a per-minute request rate with no daily cap. A page returns up to 100 full postings, so how much of the catalogue you read never changes the bill.
the licence
What a plan lets you do, in five lines.
- Store what you read and show it in your own product, commercial or not.
- Link each posting you show to its freehire page, or credit “via freehire.me”.
- Don’t resell the raw data as a dataset, download or feed of its own.
- Analyse it over time and train your own models on it.
- When the plan ends, stop showing the postings. What you derived from them — figures, trends, models — stays yours.
The full text is the data licence in our terms.
questions
Before you ask.
Can I use the freehire API in a commercial product?
Yes, with an API plan. A plan licenses you to store the postings you read and show them in your own product — a job board, a recruiting tool, an agent you sell. Without a plan the API is for personal and non-commercial use. Either way you may not resell the raw data as a dataset or feed of its own, and each posting you show links back to its freehire page or credits "via freehire.me".
Do I pay per job, per record or per request?
None of those. A plan is a flat monthly price with a per-minute request rate and no daily cap, and every request returns full postings — up to 100 per page — so the size of the catalogue you read does not change the bill.
What is the difference between the API and Data plans?
The rate. API allows 1,200 requests a minute per account, Data 6,000. Both carry the same fields, filters, company data and licence. Bulk catalogue files are coming to the Data plan; until they ship, Data is the higher rate.
Which plan fits research or skills analytics?
Usually the API plan. Analytics reads the catalogue once and then keeps up with what changed, which fits well inside 1,200 requests a minute. Take Data when you need to re-read large slices of the catalogue often. If your project needs something neither plan has yet, write to hello@freehire.me — we add features on request.
Can I keep historical postings and train models on them?
Yes, with a plan. You may keep the postings you read as a history, analyse how skills, salaries and demand change over time, and use the data to build, train and evaluate statistical or machine-learning models, including in a commercial product. What you may not do is hand the raw postings on as a dataset or feed of their own.
Is there a free tier?
Yes: the read API answers without a key, limited per address, for personal and non-commercial use. It is the same API, so you can build against it for free and switch to a key when you go live.
How do I authenticate?
Create a full-access key on your API keys page and send it as an Authorization: Bearer header. All keys of an account share the plan’s budget, and every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset so you can pace yourself.
How fresh is the data, and do closed jobs disappear?
Sources are re-crawled continuously, and a posting that leaves its source is closed rather than deleted. Search returns open postings only; a single posting fetched by its slug still answers after it closes, carrying its closed_at. A change feed with webhooks for new, updated and removed postings is the next thing we are building.
Can I cancel?
Any time, from the billing portal. The plan stays until the end of the period you paid for.
What happens to the data I stored when my plan ends?
We delete nothing on your side. Stop showing the postings in your product; you may keep what you stored for your own internal analysis. What you derived from the data — aggregated figures, trends, indicators and the models you trained — stays yours, and you may keep using it commercially as long as it does not reproduce the postings themselves.