Jobvite Integration Guide
Powered by Merge.devVisage partners with Merge.dev, the leading unified API platform, to provide a robust and secure integration with Jobvite. This guide details the technical workflows for syncing jobs, candidates, and applications between the two systems.
Integration Scope
Our integration focuses on five key workflows to automate your sourcing pipeline:
- Pull Jobs from Jobvite
- Create Applicants (Post-Consent)
- Update Candidate Status
- Smart Data Entry Points
- Duplicate Checking
Authentication
Visage connects to Jobvite using an API Key and Secret via Merge.dev's secure authentication layer. You will need to obtain these credentials from your Jobvite administrator.
1. Pull Jobs into Visage
Visage automatically imports open job requisitions from Jobvite so you can assign sourcing projects to them. We use the GET /v2/job endpoint to retrieve job details.
Data Mapped
- Job Information: Title, Requisition ID, Status
- Department: Department Name (via
GET /v2/department) - Location: Office/Remote Info (via
GET /v2/location)
2. Create Applicants
Once a candidate has replied with interest and opted in, Visage creates a new candidate record and application in Jobvite. This ensures GDPR compliance by only syncing candidates who have given consent.
Data Mapped
- Candidate Info: Name, Email, Phone
- Application: Linked to specific Job ID
- Attachments: Resume (PDF), Cover Letter
3. Update Candidate Status
Visage tracks the candidate's journey even after they are handed off to Jobvite. We poll for status updates to reflect their progress in your Visage analytics.
Polling Endpoint
GET /v2/candidateWe check for changes in the workflowState field (e.g., "Offer", "Hired", "Rejected").
Offer Details
GET /v2/candidate?include=offerWhen a candidate is hired, we retrieve offer details to attribute the hire correctly to Visage.
4. Best Entry Point
To ensure data integrity, Visage always creates candidates via the /v2/candidate endpoint rather than the generic contact endpoint. This ensures that every Visage-sourced profile is immediately treated as an actionable applicant linked to a specific requisition.
Why this matters
Creating records as "Candidates" instead of "Leads" ensures they appear in your recruiter's primary workflow, reducing the risk of them being ignored in a general talent pool.
5. Duplicate Checks
Before creating any new record, Visage performs a real-time duplicate check against your Jobvite database.
| Check Method | Logic | Action |
|---|---|---|
| Email Match | Exact match on email field | Update existing candidate record |
| Phone Match | Exact match on normalized phone | Flag as potential duplicate for review |
Sync Frequency
Data sync frequencies vary by object type. Below are the standard sync intervals provided by the Merge.dev integration.
| Common Model | Daily Sync | Highest Frequency |
|---|---|---|
| Application | 24 hours | 1-5 minutes |
| Candidate | 24 hours | 1-5 minutes |
| Job | 24 hours | 1-5 minutes |
| Department | 24 hours | 1-5 minutes |
* "Highest Frequency" requires the Force Resync option or specific plan upgrades.