Before you start
You need a JazzHR user who can see the account's API key. JazzHR shows it only to Super Admins, Recruiting Admins and Developers. JazzHR says its API is included with every subscription level.
You will paste one thing into Metaintro: your JazzHR API key.
Create the credential in JazzHR
JazzHR gives each account one API key. You don't create a new one, you copy it.
Sign in to JazzHR as a Super Admin, Recruiting Admin or Developer.
Select Settings, then Integrations.
Copy the string of letters and numbers in the API Key field at the top of the page.
JazzHR's guide: API Overview.
The key gives access to your whole JazzHR account. Keep it private and paste it only into Metaintro.
Connect in Metaintro
Go to Settings > Integrations.
Choose JazzHR.
Paste the key into API key.
Select Connect.
Then map your Metaintro jobs to JazzHR jobs, set your rules, check the preview and go live.
What Metaintro sends and reads
Metaintro only sends people who chose to share their profile with you for a job.
Candidate: Metaintro adds the person to JazzHR with their name, email and phone, and sets the source to Metaintro. If they are already in JazzHR on that job, Metaintro uses the existing record.
Application: the person is added to the mapped JazzHR job.
Résumé: sent with the new candidate when they have one. For someone already in JazzHR, it is added as a file.
Note: a note visible to your hiring team, with a link to their proof card and a short summary.
Stage updates: Metaintro checks each candidate's workflow step in JazzHR regularly and updates their status in Metaintro. JazzHR has no stage-change alerts for this, so updates are not instant.
Metaintro reads your JazzHR jobs so you can map them.
Limits
Stage moves happen in JazzHR. Metaintro reads stages but does not move candidates between steps.
JazzHR needs an email for each candidate, so people without one can't be sent.
Before adding someone, Metaintro checks every applicant on the job for the same email. On jobs with many applicants this check can take a few minutes.
Metaintro only checks the applicants on the mapped job. Someone already in JazzHR for a different job is added as a new candidate.
If a delivery is retried, the note may appear twice. JazzHR doesn't let Metaintro check its existing notes.
JazzHR doesn't publish rate limits. Metaintro paces its requests and waits when JazzHR asks it to slow down.
If something goes wrong
Key rejected: copy the key again from Settings > Integrations and reconnect. Check that the user who copied it is still a Super Admin, Recruiting Admin or Developer.
A candidate didn't arrive: check that the Metaintro job is mapped to an open JazzHR job. If two JazzHR applicants on the job share the person's email, Metaintro stops rather than guess. Merge or fix the duplicate in JazzHR.
Rate limited: Metaintro waits and tries again on its own. You don't need to do anything.
Stage looks out of date: stages are checked regularly, not instantly. Give it some time after a change in JazzHR.