Job posting API: one endpoint for every job on the web
If you've ever shopped around for a job-posting API and ended up with three vendors, four scrapers, and a deduplication script - this post is for you.
Dvir Atias
Founder, JobsPipe
If you’ve ever shopped for a “job posting API” and ended up with three vendors, four scrapers, and a Python script to dedupe the overlap - this post is for you. A single normalized job-posting endpoint is the foundation for any product that touches hiring data, and it’s harder to build well than it looks.
Why three vendors
Most jobs-data products end up multi-vendor because no single vendor covers everything. JSearch has Indeed but not Workday. Coresignal has historical bulk but no real-time webhooks. ScrapingDog is great for one site but you maintain the normalization yourself. So you glue them together, write a dedup script, and add monitoring for each one.
What “unified” actually means
A real unified job-posting API needs four things at minimum:
- Source breadth - at least 20+ ATSs and the major boards. Anything less means you still need a second vendor.
- One JSON schema - same fields, same types, regardless of source. Otherwise your application code branches per source and you’ve gained nothing.
- Cross-source dedup - the same job posted to a Greenhouse board and mirrored to Indeed must collapse into one record. Without this, you ship duplicates to your downstream UI.
- Parsed structured fields - salary, location, remote flag, all extracted from free text into machine-readable types. Otherwise “structured data” is a marketing claim, not a feature.
JobsPipe’s endpoint
curl https://api.jobspipe.dev/v1/jobs/search \
-H "Authorization: Bearer jp_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "job_title_or": ["staff engineer"], "posted_at_max_age_days": 1 }'Returns every matching job across every source we index, deduped, with parsed comp, in one paginated response. Add source_or to scope to one source or source_not to exclude aggregator listings.
One endpoint, every job - free tier with monthly credits.
Get a free API key
Frequently Asked Questions
What is a job posting API?
A job posting API is a single endpoint that returns job listings from many sources in one normalized shape. A genuinely unified one needs four things: source breadth covering at least 20 ATSs plus the major boards, one JSON schema with the same fields and types regardless of source, cross-source dedup so a job posted to Greenhouse and mirrored to Indeed collapses into one record, and parsed structured fields for salary, location, and remote status.
Why do teams end up using multiple job data vendors?
Because no single vendor covers everything, most jobs-data products end up multi-vendor. JSearch has Indeed but not Workday. Coresignal has historical bulk but no real-time webhooks. ScrapingDog is great for one site but you maintain the normalization yourself. So teams glue them together, write a dedup script, and add monitoring for each one, which is exactly the overhead a unified endpoint is meant to remove.
How do I query every job source with one API call?
Send one request to a unified endpoint and filter within it, rather than calling each vendor separately. With JobsPipe you post to /v1/jobs/search with fields like job_title_or and posted_at_max_age_days, and it returns every matching job across every source it indexes, deduped, with parsed compensation, in one paginated response. Add source_or to scope to a single source, or source_not to exclude aggregator listings.