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.
- No key needed to try
- Flat monthly price
- Cancel any time
- Open source
curl "https://hireplz.in/api/v1/jobs/search?q=golang&countries=de&limit=3" # with a plan: -H "Authorization: Bearer $HIREPLZ_API_KEY"
{
"data": [{
"title": "Golang Software Engineer",
"company": "1global",
"source": "workable",
"url": "https://apply.workable.com/j/973E5FE25D",
"countries": ["de", "pt"],
"cities": ["Berlin", "Lisbon"],
"skills": ["go", "grpc", "kafka", "kubernetes", "postgresql"],
"category": "software_engineering",
"summary": "Builds and maintains scalable backend systems in Go…",
"posted_at": "2026-11-03T00:00:00Z",
"closed_at": null
}, …],
"meta": { "total": 142, "limit": 3, "offset": 0 }
}- ATS platforms read directly
- 181
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.
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, metros, 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
- Enrichment
- a one-line summary, the requirements split into required and preferred, years of experience
- Reality signal
- stale, reposted and mass-posted flags, so you can hide ghost jobs
- 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
One flat price, however much you read.
The usual job-data pricing meters every record: around $100 a month buys tens of thousands of postings, and mirroring a catalogue of millions runs to thousands. Here the bill does not move with how much you read.
| Feature | hireplz | Record-metered API | Your own crawler |
|---|---|---|---|
| What you pay for | A flat monthly plan | Every record you read, plus overage | Engineers, proxies and servers |
| Try it before you pay | Without a key or a card | A trial, after sign-up | Weeks of building first |
| Full description in every result | Up to 100 postings a page | Often a separate call | Whatever you manage to parse |
| De-duplicated across sources | Reposts collapsed | Varies | You build it |
| Company profile on each posting | Included | Often a paid add-on | You build it |
| Licence to show it in your product | Plain, published in our terms | Per contract | Your own legal risk |
| MCP server for AI agents | Included | Rare | You build it |
| Sales call to start | Never | Often, for volume | Not needed |
From first request to production in an afternoon.
1 Call it now
The read API answers without a key. Run the request above, or point your code at it and build.
2 Pick a plan, create a key
Subscribe below, create a full-access key on your API keys page and send it as a Bearer header.
3 Ship
A posting that leaves its source is closed, not deleted, and says so in closed_at — your product stays honest.
Read it the way your product works
What a plan lets you do, in four lines.
- Store what you read and show it in your own product, commercial or not.
- 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.
Check our work before you buy.
Before you ask.
Something missing? Write to [email protected] — we add features on request.
Can I use the hireplz 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.
Do I pay per job, per record or per request?
None of those. A plan has a flat monthly price, 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?
Both carry the same fields, filters, company data and commercial-use licence. The Data plan adds a daily bulk file of the whole open catalogue (gzip JSON Lines), listed at GET /api/v1/catalogue/snapshots.
Which plan fits research or skills analytics?
The API plan includes the fields, filters and licence needed for research and skills analytics. If your project needs something it does not offer, write to [email protected] — 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 for personal and non-commercial use. It is the same API, so you can build against it for free and switch to a plan 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. Signed-in MCP and CLI connections can also authenticate through OAuth.
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.
Your first request takes ten seconds.
No key, no card, no sales call. Paste it into a terminal, then take a plan when you ship.
curl "https://hireplz.in/api/v1/jobs/search?q=python&countries=us&limit=10"