Every job posting, one API.

What is JobsPipe?

JobsPipe is a unified Jobs API that returns normalized, deduplicated job postings from 30+ applicant tracking system (ATS) feeds and job boards as a single JSON schema, alongside a company tech-stack scanner that reveals the technologies a company runs. It is developer-first: you authenticate with an API key, call one endpoint, and get clean, structured records instead of brittle scrapers. A free tier with 5,000 requests per month lets you evaluate the API without a credit card.

JobsPipe by the numbers

30+

ATS and job-board sources

1

normalized JSON schema for every posting

5,000

free API requests per month, no card

$49 / $299

Builder / Scale plans per month

2-50

requests per second, by plan tier

~14 days

tech-stack scan cache window

Key facts

• 30+ sources, spanning applicant tracking system (ATS) feeds and job boards such as Greenhouse, Lever, Ashby and Workday.
• One normalized JSON schema for every posting: stable ID, title, company, location, parsed salary range, remote flag, posted date, apply URL and full description.
• 5,000 free requests per month with no credit card required on the Free tier.
• Plans: Free, Builder ($49 per month), Scale ($299 per month).
• Results are deduplicated across sources, so a role posted to two ATS systems collapses into one record with every origin listed under source_refs.
• Parsed salary ranges expose minimum, maximum and currency as structured fields rather than free text.
• Company tech-stack scans are cached for roughly 14 days to keep technographic lookups fast and cheap.
• Real-time webhooks fire when a job opens, changes or closes, so you never poll the full index.

How developers use the JobsPipe API

JobsPipe vs building it yourself

Sources covered by JobsPipe

JobsPipe normalizes job postings from these applicant tracking systems and job boards into one schema. Each links to a page documenting its coverage and how to pull its postings through the API.

• Workday - Every public posting from every public Workday tenant - one normalized endpoint, no per-tenant OAuth.
• Paycom - Every public Paycom career site, one endpoint. No per-customer credentials, no scraper to maintain.
• Indeed - Indeed deprecated its Publisher API. JobsPipe gives you the data anyway - normalized, fresh, and included.
• Glassdoor - Glassdoor retired its public API in 2022. JobsPipe normalizes Glassdoor jobs into a developer-friendly schema.
• Ashby - Ashby's Job Board endpoint covers one company at a time. JobsPipe covers every public Ashby customer in one call, in the same JSON shape as 30+ other ATSs.
• Workable - Every public Workable career site, one endpoint. No per-customer API keys to juggle.
• Lever - Every public Lever posting, one endpoint. Same schema as Workday, Indeed, and 30+ other sources.
• SmartRecruiters - SmartRecruiters' Postings API works one customer at a time and is tier-dependent. JobsPipe covers every public SmartRecruiters customer in one call, in the same JSON shape as 30+ other ATSs.
• iCIMS - The iCIMS Talent Cloud API is partner-only. JobsPipe covers every public iCIMS customer with no application form, no OAuth, and the same JSON shape as 30+ other ATSs.
• Pinpoint - Every public Pinpoint career site, one endpoint. Same schema as Workday, Indeed, and 30+ other sources.
• JazzHR - Every public JazzHR career site, one endpoint. No per-customer API onboarding.
• Manatal - Every public Manatal-hosted careers site, one endpoint. Recruiting agencies and in-house teams both covered.
• Breezy HR - Every public Breezy HR career site, one endpoint. No need to enumerate company slugs.
• Greenhouse - Every public Greenhouse Job Board posting, one endpoint. No per-tenant Harvest API onboarding, no slug discovery.
• BambooHR - Every public BambooHR posting, normalized - no per-tenant API key, no embed-widget reverse engineering.
• Paylocity - Every public Paylocity posting, one endpoint - no partner-program approval, no per-tenant integration build.
• LinkedIn - The LinkedIn Jobs API doesn't exist anymore. Go upstream to where each job was first posted - legally.
• ZipRecruiter - ZipRecruiter postings without the Partner API gating - one endpoint, normalized, no inbound feed contract.
• SAP SuccessFactors - Every public SuccessFactors posting, one endpoint - no OData URL hunting, no per-data-center URL juggling.
• Zoho Recruit - Every public Zoho Recruit posting across every region, one endpoint - no per-region OAuth client.
• Jobvite - Every public Jobvite posting across Hire, Engage, and Enterprise, one endpoint - no per-tenant Job Feed enablement.
• Taleo - Every public Taleo Enterprise + Taleo Business Edition + Oracle Recruiting Cloud posting, one endpoint - normalized.
• Teamtailor - Every public Teamtailor posting, one endpoint - no per-tenant X-Api-Key, no JSON:API pagination to flatten.
• Personio - Personio runs HR for 14,000+ companies across Europe - most aggregators miss it. JobsPipe normalizes every public Personio posting into the same shape as Workday, Greenhouse, and 30+ other sources.
• USAJobs - USAJobs has the best-documented public job API of any source. JobsPipe normalizes it into the same shape as Workday, Greenhouse, Lever, and 30+ other ATSs.
• Recooty - Recooty doesn't publish a developer API - just branded careers pages and a job widget. JobsPipe indexes every public Recooty tenant and returns the data in the same JSON shape as Workday, Greenhouse, and 30+ other sources.
• Trakstar - Trakstar Hire publishes per-tenant RSS feeds and HTML careers pages - no public JSON API. JobsPipe flattens both into the same JSON schema as Workday, Greenhouse, and 30+ other sources.
• Polymer - Polymer publishes a public jobs endpoint - but per-organization. JobsPipe indexes every public Polymer org and returns the data alongside 30+ other sources in one normalized JSON schema.
• Comeet - Comeet (now Spark Hire Recruit) ships a Careers API designed for one customer's own site - not for aggregators. JobsPipe normalizes every public Comeet tenant into the same JSON shape as 30+ other sources.
• Rippling - Public job postings from companies that use Rippling Recruiting, one endpoint - same schema as 30+ other sources.
• Dayforce - Public job postings from Ceridian Dayforce career sites, one endpoint - same schema as 30+ other sources.
• Bullhorn - Public job postings from staffing agencies that run Bullhorn, one endpoint - same schema as 30+ other sources.
• Oracle Recruiting Cloud - Public job postings from companies running Oracle Recruiting Cloud, one endpoint - same schema as 30+ other sources.
• Cornerstone - Public job postings from companies that run Cornerstone Recruiting, one endpoint - same schema as 30+ other sources.

Glossary: jobs-data and hiring-intent terms

ATS API

An ATS API is the programmatic interface an applicant tracking system exposes so software can read or write recruiting data - job requisitions, candidates, applications, and interview stages - without going through the ATS web interface.

ATS integration

ATS integration is the work of connecting an applicant tracking system to other software - a job board, a sourcing tool, an HRIS, an analytics product - so recruiting data moves between them automatically instead of by manual export.

Job board API

A job board API is a programmatic interface for reading job postings - title, company, location, salary, description, apply link - usually across many employers, so software can ingest listings without scraping web pages.

Job aggregator

A job aggregator is a system that collects job postings from many sources - company career pages, applicant tracking systems, and other boards - and combines them into a single searchable, deduplicated index.

Job posting schema

A job posting schema is the defined structure of a job record - the field names, types, and meanings - that lets job data from different sources be stored, searched, and exchanged consistently.

Job posting deduplication

Job posting deduplication is the process of detecting that several collected job records describe the same real-world opening and collapsing them into one, so an aggregated index does not count the same job many times.

Unified API

A unified API is a single API that abstracts many similar third-party services behind one schema and one authentication flow, so a developer integrates once instead of once per provider.

Talent intelligence

Talent intelligence is the practice of collecting and analyzing workforce data - job postings, skills, compensation, hiring activity, talent movement - to make better decisions about recruiting, workforce planning, and competitive strategy.

Job scraping

Job scraping is the automated extraction of job postings from websites - company career pages, job boards, and ATS-hosted listings - by programmatically fetching pages and parsing the posting data out of them.

API rate limiting

API rate limiting is the practice of capping how many requests a client can make to an API within a set time window, protecting the service from overload and enforcing fair use across all consumers.

Intent data

Intent data is any signal that suggests an account or buyer is moving toward a purchase decision - inferred from third-party content consumption, software-review activity, first-party website engagement, or capital-allocation moves like hiring.

Hiring-signal intent

Hiring-signal intent is a category of B2B intent data that uses a company's open job postings and headcount changes as a leading indicator of buying intent - typically 1-2 quarters before content or review intent fires.

Technographics

Technographics is data about the technology stack a company runs - its frameworks, analytics, hosting, CRM, payments, and other tools - used by B2B teams to target and qualify accounts by the software they already use.

Technographic data

Technographic data is structured data on the technologies a company uses, attached to its domain, exposed via API so sales, marketing, and competitive-intelligence teams can target and segment by tech stack.

Firmographic vs technographic data

Firmographic data describes a company's attributes (industry, size, revenue, location); technographic data describes the technologies it uses. B2B teams combine both to define and prioritize target accounts.

B2B technographic data

B2B technographic data is technology-usage data on companies, used by sales, marketing, and competitive-intelligence teams to build target lists, qualify accounts, and personalize outreach around the tools a prospect already runs.

Technographic segmentation

Technographic segmentation is the practice of grouping accounts by the technologies they use, so messaging, targeting, and prioritization can be tailored to each group's stack.

Technographic data examples

Technographic data examples are the concrete technology data points attached to a company, such as the analytics suite, hosting provider, ecommerce platform, CRM, or payment processor it uses.

Employment Type

Employment type is the field on a job posting that records the kind of working relationship an opening offers - full-time, part-time, contract, temporary, or internship - using a small, fixed set of values so jobs can be filtered and compared across sources.

Frequently asked questions