Connect Jobvite to Metaview
Setting up Jobvite is a two-step process: first request the required API access from Jobvite, then connect the integration in Metaview.1. Request API access from Jobvite
Jobvite requires API access to be explicitly enabled before Metaview can connect. To do this, email your Jobvite representative (or Jobvite support) and request access to the following endpoints:- Job v2 (Hire)
GET /job
- Candidate v2
GET /candidateGET /workflowGET /dispositionGET /customfield (objectType=Candidate)GET /customfield (objectType=Job)PUT /candidate
- CreateCandidate
POST /candidate
We recommend requesting all of the endpoints above so the whole integration is available. The
GET endpoints are required for the core integration; the PUT and POST endpoints are only needed to write back to Jobvite. See Permissions for the breakdown.2. Connect in Metaview
Once Jobvite has enabled the endpoints above, go to Settings → Integrations in Metaview, find Jobvite, and click Connect. Follow the on-screen flow to complete the setup.Permissions
Jobvite enables API access endpoint by endpoint, so Metaview’s access is exactly the set of endpoints you request from Jobvite. The connection itself is authorized through Kombo. Metaview uses that access to match your calls to the right candidate and role, enrich candidate profiles, keep your team in sync, and write Notes and other Metaview information back to Jobvite.Kombo is a Metaview subprocessor. Our current subprocessor list is published in the Trust Center, and the terms covering this processing are set out in our DPA. See also Privacy and security.
View list of permissions
View list of permissions
Required
GET /job(Job v2)GET /candidateGET /workflowGET /dispositionGET /customfield(objectType=Candidate)GET /customfield(objectType=Job)
PUT /candidatePOST /candidate- Application attachment writes
We recommend requesting all of the endpoints above so the whole integration is available. If Jobvite enables only the required endpoints, the core integration still works — you just won’t be able to write back to Jobvite.
Features
Integrating your Jobvite ATS to Metaview unlocks the following features:- Employees sync
- Enhanced candidate metadata (e.g. name, job title, stage, location, CV)
- Ability to post your Notes to ATS with one click
- Add your Notes as an attachment to the candidate’s application
- Automatic addition of links to Metaview notes in your ATS
- Use Application Review to screen candidates
- Use Sourcing to search through your ATS for potential candidates
- Add new candidates to your ATS that have been sourced
- Move candidates to different stages in your pipeline
- Reject applications directly from Metaview
Jobvite logo to go to the matched entry in your ATS.
What’s not supported
- Automatic scheduling — Schedule interviews through your connected calendar. Metaview will then match the call to Jobvite data.
Troubleshooting
Since Jobvite does not support automatic scheduling, Metaview will attempt to match calls scheduled through your connected calendar to relevant Jobvite records. The most common reasons why this doesn’t happen automatically are:- Call or candidate is missing in the ATS
- Duplicate calls or candidates in the ATS
- Data mismatch between Metaview invite and information in ATS (e.g. wrong participants, missing participant, wrong candidate)
- Insufficient information to match call or candidate (often occurs when using Inviting to an ongoing call or Upload recordings options)
- The meeting type is NOT set to Job interview or Debrief. Please see Call details for more information.
Disconnect your Jobvite integration
You can disable your Metaview integration directly from within your Metaview account underSettings → Integrations then select Disconnect Jobvite.
This immediately disconnects Metaview from your ATS data. Please note however that any calls that have already been scheduled may still go ahead. Please see Disabling Metaview for details on how to also make sure that the Notetaker bot doesn’t join any future calls.