Source · JazzHRJazzHR Jobs API.
Every public JazzHR career site, one endpoint. No per-customer API onboarding.
Why people are confused about the JazzHR API
JazzHR offers an XML feed and a REST API to subscribers, but both are scoped to each customer's account with their own API key. There is no public cross-customer endpoint for aggregating jobs across the JazzHR universe.
JazzHR customers host their careers pages at app.jazz.co/<company> (or app.jazzhr.com on legacy accounts), with custom embeds available on customer-owned domains. JobsPipe indexes every public JazzHR careers page and normalizes the data into the same schema as our other sources.
Possible per customer with their subscription credentials. Not a path to multi-tenant coverage.
Technically possible. Each customer is its own scraper config, subject to JazzHR's rate limits.
Every public JazzHR customer, one endpoint, same JSON schema as the rest of JobsPipe.
JazzHR API documentation
JazzHR developer documentation lives at api.resumatorapi.com (the legacy host that JazzHR still uses internally - JazzHR was previously branded as The Resumator). The main surfaces are the Listings XML feed and the REST API for applicants, candidates, jobs - both scoped per customer with that customer's API key. JazzHR does not expose a cross-customer aggregator endpoint. JobsPipe's documentation at /docs covers the normalized JSON schema we return for every public JazzHR careers page.
JazzHR API key
JazzHR API keys are minted inside the customer's JazzHR admin under Settings > Integrations. Each key is subscription-tier-gated (some keys require Plus or Pro plans) and customer-scoped. JobsPipe doesn't request JazzHR credentials - we consume only public-facing JazzHR careers pages and authenticate with one JobsPipe key.
JazzHR API integration
Single-customer JazzHR integration requires that customer to mint you a key on a qualifying plan. Cross-customer aggregator integration is JobsPipe: every public JazzHR customer, one endpoint, same normalized JSON schema as 30+ other ATSs - no per-customer key juggling.
Sample request
curl "https://api.jobspipe.dev/v1/jobs?source=jazzhr" \
-H "Authorization: Bearer $JOBSPIPE_KEY" \
-H "Accept: application/json"Sample response
{
"id": "jz_M2Y0YjJlMDgtNWFlNg",
"source": "jazzhr",
"tenant": "nextlevel",
"title": "Customer Success Manager",
"company": "NextLevel Software",
"location": {
"city": "Austin",
"region": "TX",
"country": "US",
"remote": true
},
"salary": {
"min": 72000,
"max": 95000,
"currency": "USD",
"period": "year",
"source": "explicit"
},
"employment_type": "full_time",
"posted_at": "2026-05-13T18:20:00Z",
"expires_at": null,
"apply_url": "https://app.jazz.co/apply/nextlevel/...",
"description": "NextLevel is hiring a Customer Success Manager to grow our mid-market book across the US ..."
}Every JazzHR job record is returned in the same JSON shape as every other JobsPipe source. The full schema is documented in the docs.
Fields in every JazzHR job record
FAQ
Does JobsPipe need a JazzHR API key per customer?+
No. JobsPipe consumes only public-facing JazzHR careers data. We don't require per-customer subscription credentials.
How fresh is JazzHR data?+
Every JazzHR customer's careers site is re-crawled at least every 24 hours.
Are JazzHR jobs deduped against other sources?+
Yes. When the same posting appears on JazzHR and on Indeed/Glassdoor/etc, JobsPipe links them as one canonical job record.
Which JazzHR plans does JobsPipe cover?+
JobsPipe indexes any JazzHR customer whose careers page is publicly accessible. Internal-only postings (set to private in JazzHR) are not crawled.
Try JazzHR data free - 5,000 requests/month, no credit card.
Get a free API key