--- title: "JazzHR API" description: "JazzHR API: the per-account REST API and XML feed, the app.jazz.co careers pages where openings are public, and how to reach JazzHR employers in one call." canonical: https://jobspipe.dev/sources/jazzhr date_published: 2026-06-16 date_modified: 2026-09-26 author: Dvir Atias --- # JazzHR API JazzHR gives each subscriber an XML job feed and a REST API keyed to that one account, with no public cross-customer endpoint; openings are public at app.jazz.co/ or on the customer's own domain. JobsPipe does not collect JazzHR; the same employers' openings reach one search endpoint through the boards JobsPipe does collect, in one record shape across 30+ sources. > JazzHR has no public cross-employer jobs API, and JobsPipe does not collect JazzHR. This page explains what JazzHR exposes and how to reach the same employers through the boards JobsPipe does collect. **Canonical URL:** https://jobspipe.dev/sources/jazzhr ## Coverage JobsPipe does not collect JazzHR. This page explains what JazzHR exposes publicly and how to reach the same postings where they are also published on a board JobsPipe does collect (Workday, Greenhouse, Lever, Ashby, LinkedIn, Indeed, SmartRecruiters, Workable, Personio, Recruitee, Teamtailor, EURES, Paylocity, Breezy HR, CV-Library, Y Combinator, Bayt, JobTech (Sweden), Resume-Library, Arbeitnow, Himalayas, Rise, Manatal, Pinpoint, JobScore, HireHive, The Muse, Remotive, Remote OK, Jobicy, Working Nomads, Landing.jobs). ## Why JazzHR jobs data is confusing JazzHR gives each subscriber an XML job feed and a REST API keyed to that account. Both read one customer's data with that customer's API key; there is no public cross-customer endpoint. JazzHR customers publish openings at app.jazz.co/ (app.jazzhr.com on older accounts) or on their own domains through embeds, and JazzHR syndicates postings to job boards on the customer's behalf. There is no customer directory. JobsPipe does not collect JazzHR. Employers that run JazzHR usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. ## Workarounds ### Get API access from each JazzHR customer Each customer generates an API key inside JazzHR and can share it with you. One key reads one account. ### Scrape app.jazz.co careers pages Possible per employer you already know. The pages are public HTML; discovery and upkeep are on you. ### What JobsPipe offers instead JobsPipe does not collect JazzHR. Search the same employers by name across the boards JobsPipe does collect (LinkedIn, Indeed, Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever and Paylocity); sources[0].provider on each record names the board it came from. ## Fields available on every record - `id` - `job_title` - `company` - `company_domain` - `url` - `date_posted` - `discovered_at` - `last_seen_at` - `verified_at` - `status` - `closed_at` - `closed_reason` - `ghost_score` - `seniority` - `cities` - `state_code` - `min_annual_salary_usd` - `max_annual_salary_usd` - `technology_slugs` - `keyword_slugs` - `esco_skills` - `sources` ## FAQ ### Where are JazzHR job postings hosted? JazzHR customers publish openings at app.jazz.co/, or app.jazzhr.com on older accounts, or on their own domains through embeds. The pages are public HTML, so you can read them per employer you already know, but discovery and upkeep are on you. JazzHR also syndicates postings to job boards on the customer's behalf. ### Where is the API key in a JazzHR account? Inside a JazzHR account an admin opens Integrations, then API, and copies the account's key. That key reads the account's REST API and XML job feed for that one company only. JazzHR does not issue developer keys that read other customers' jobs, so an outside developer needs each customer to share its key individually. ### Does JazzHR have an XML job feed? Yes, per subscriber. JazzHR gives each account an XML job feed alongside its REST API, and both read one customer's data with that customer's API key. There is no public feed that spans JazzHR customers, so a multi-employer product would need a key from every account it wants to read. ### Is there a list of companies using JazzHR? No. JazzHR publishes no customer directory and has no public cross-customer endpoint. Employers that run JazzHR usually also post the same roles to LinkedIn and Indeed, and JobsPipe collects those boards, so filtering POST /v1/jobs/search by company_name_partial_match_or reaches a known employer's postings, with sources[0].provider naming the board each record came from. ## Does JazzHR have an API? JazzHR gives each subscriber an XML job feed and a REST API keyed to that account. Both read one customer's data with that customer's API key; there is no public cross-customer endpoint. JazzHR customers publish openings at app.jazz.co/ (app.jazzhr.com on older accounts) or on their own domains through embeds, and JazzHR syndicates postings to job boards on the customer's behalf. There is no customer directory. ## What JobsPipe returns for JazzHR Nothing under "source_or": ["jazzhr"]: JobsPipe does not collect JazzHR. Employers that run JazzHR usually also post the same roles to LinkedIn and Indeed, and larger ones run Workday, Greenhouse, Workable, SmartRecruiters, Ashby, Lever or Paylocity alongside it. JobsPipe collects all of those boards, so filter POST /v1/jobs/search by company_name_partial_match_or to reach them. Each record comes back with sources[0].provider, status, ghost_score, discovered_at, last_seen_at, seniority, and min_annual_salary_usd and max_annual_salary_usd when the posting states a range. ## Related - **Product:** https://jobspipe.dev/jobs-api - **All sources:** https://jobspipe.dev/sources - **Docs:** https://docs.jobspipe.dev - **Sign up (free tier):** https://jobspipe.dev/signup --- Generated from structured data. View the rendered page at https://jobspipe.dev/sources/jazzhr. --- Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup: ```bash curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search ``` Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin