The API Report CardAPI Index
JazzHR

JazzHR API

Enterprise / HR / ERP · jazzhr.com

JazzHR publishes a public REST API at apidoc.jazzhrapis.com covering applicants, jobs, users, hires, and activities, plus Apply, Assessment, and Screening APIs. API access requires the Pro plan near $420 to $499 per month, and webhooks only cover candidate export events.

Last verified: October 2026HR & PayrollNO MCP
API GRADE
A+
VERIFIED OCT 2026

SCORECARD

ExistenceGOODPublic REST API plus dedicated Apply, Assessment, and Screening surfaces, all documented at apidoc.jazzhrapis.com.
AccessGOODKeys are self-serve on the Pro plan, roughly $420 to $499 per month, sometimes with a per-key surcharge.
CoverageGOODApplicants, jobs, users, hires, notes, and activities; no bulk export, so full syncs mean paginated walks.
AuthPOORPer-tenant API key is passed as a query parameter, surfacing the secret in logs and proxy chains; no OAuth for the core API.
Docs & DXGOODEvery surface is publicly documented without login; aggregator SDKs (Merge, Knit) stand in for missing first-party ones.
StabilityGOOD
MCPNONENo official or community MCP server was found for JazzHR. The only GitHub hits touching the name are job scraping utilities, not an MCP server for the applicant tracking system. VERIFIED 2026-08
Supergood turns hard-to-integrate enterprise software into clean REST APIs and MCP tools: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

JazzHR scores A+ on Supergood's API Report Card. JazzHR publishes a public REST API at apidoc.jazzhrapis.com covering applicants, jobs, users, hires, and activities, plus Apply, Assessment, and Screening APIs. API access requires the Pro plan near $420 to $499 per month, and webhooks only cover candidate export events.

Tried to integrate with JazzHR?
SOURCES
API access is gated to the top-tier Pro plan (~$420-$499/mo) and may require an additional per-API-key fee, which puts it out of reach of Hero and Plus customers help.jazzhr.com ↗
Rate limits are not formally documented in the public API portal, integrators must guess at safe throttling thresholds and reverse-engineer behavior from 429 responses apidoc.jazzhrapis.com ↗
Webhooks are limited to Candidate Export events, high-value events like job created, offer signed, hire completed, and stage change are not all natively delivered as webhooks; integrators end up polling apidoc.jazzhrapis.com ↗
Pagination is page-based without a documented total count, making 'why is data missing?' reconciliation against the UI fiddly apidoc.jazzhrapis.com ↗
No bulk export endpoint; full historical syncs require paginated walks across applicants, jobs, hires, and activities, which is slow on larger tenants docs.merge.dev ↗
API key is passed as a query parameter rather than a header, which surfaces secrets in logs, browser history, and proxy chains if integrators are not careful endgrate.com ↗
Webhook delivery retries are limited; long customer-endpoint outages result in dropped events with no built-in replay, forcing integrators to run a parallel reconciliation poll apidoc.jazzhrapis.com ↗
No first-party SDKs in any language; integrators rely on community examples or unified-API aggregator SDKs (Merge, Knit, Apideck) apitracker.io ↗
Limited write-side capability on some object types (workflow steps, custom fields, user roles); structural changes typically require the UI developers.getknit.dev ↗
Sandbox environment availability is limited; partners often test against production tenants with throwaway data apidoc.jazzhrapis.com ↗
Documentation has migrated locations (originally GitHub at JazzHR/api-doc, now apidoc.jazzhrapis.com) and is reference-grade but light on end-to-end guides for common flows (initial historical sync, incremental sync, webhook + poll reconciliation) github.com ↗
OAuth 2.0 is not supported on the core REST API, only API-key auth, which is coarse and harder to scope or revoke per-user/per-partner apidoc.jazzhrapis.com ↗
Billing / cancellation lock-in: customers report being locked into year-long contracts with no way out, continued billing after cancellation requests, and weeks of unresponsive support before refunds trustpilot.com ↗
Customer support is slow and inconsistent, with multiple tickets going unanswered or requiring repeated follow-up; premium support is a paid add-on at ~$49/month trustpilot.com ↗
Data migration from other ATS platforms is botched, historical records dumped with no structure and rendered unusable trustpilot.com ↗
Applicant flow drops off mid-contract, customers report receiving applicants for the first 6 months of an annual subscription and then none, with JazzHR pointing the finger at job boards rather than owning the issue trustpilot.com ↗
Calendar sync issues with Google Calendar / Office 365 and document upload glitches impact daily workflow efficiency capterra.com ↗
UI feels dated relative to modern competitors (Workable, Breezy, Ashby), clunky navigation, minimal mobile optimization, extra clicks for simple actions hrtechfeed.com ↗
Reporting and analytics are shallow, basic hiring metrics only; advanced reporting is a paid add-on at ~$59/month g2.com ↗
AI capabilities (resume parsing, intelligent candidate ranking, automated interview scheduling) lag modern AI-first ATS competitors skima.ai ↗
Hero plan caps at 3 active jobs and Plus caps at 200, customers report being forced into the more expensive Pro plan ($420-$499/mo) earlier than expected leonstaff.com ↗
Add-on creep: candidate texting ($39/mo), eSignature ($59/mo), advanced reporting ($59/mo), Zoom integration ($29/mo), and premium support ($49/mo) are separate line items on top of base pricing pin.com ↗
Customization and reporting capabilities are limited compared to Greenhouse / Workable / Ashby avahr.com ↗
Post-Employ-acquisition feature velocity has slowed, with long-standing feature requests still outstanding in 2025-2026 g2.com ↗