Skip to content
Human resources ⇄ Database

Jobvite to Reltio integration — real-time, two-way sync

Keep Jobvite and Reltio in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Jobvite and Reltio

Put your workforce data where your apps can reach it: Reltio and Jobvite share the same people, positions, and org structure in real time.

Jobvite is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Reltio is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Application, Workflow Status, New Hire, Employee in Jobvite need to exist as queryable Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM) in Reltio before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.

Stacksync syncs Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM) in Reltio with Application, Workflow Status, New Hire, Employee in Jobvite field by field, in real time. You decide which system owns which fields — Jobvite typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.

The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.

Common use cases

  • 01 Feed Interactions (transactions, visits, events) into Reltio to enrich entity profiles, then read them back for 360-degree reporting.
  • 02 Mirror the Reltio Activity Log and change history into a database for audit, lineage, and governance reporting.
  • 03 Consolidate Applications, Offers, and Workflow Status into a warehouse for time-to-fill and funnel reporting across every requisition.
  • 04 Sync Employee roster data into Jobvite with POST /employee to power employee-referral matching and internal-mobility postings.

Common sync patterns

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Jobvite stay consistent in Reltio, so hierarchy-driven logic and permissions don't drift.

Computed and operational fields flow back

Values assembled or corrected in Reltio write onto the matching record in Jobvite where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Jobvite land as queryable Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM) in Reltio, so internal apps and dashboards read live data instead of a periodic export.

What you can sync between Jobvite and Reltio

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Jobvite objects Reltio objects How this pairing syncs
Application Links a candidate to one requisition with its workflow state; read for pipeline reporting and status written back through the candidate update call. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Application is specific to Jobvite and Activity Log to Reltio — each maps to any object or custom field on the other side.
Workflow Status The pipeline stage per application (Screen, Interview, Offer, Hired); updated through POST /candidate/updateCandidates to advance records. Data Change Requests (DCR) Stewardship change proposals routed through approval workflows; read and written to feed or track governed edits to golden records. Workflow Status is specific to Jobvite and Data Change Requests (DCR) to Reltio — each maps to any object or custom field on the other side.
New Hire Hired-candidate records surfaced in the candidate feed and via the candidate hired webhook; commonly written into an HRIS or onboarding tool. Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. New Hire is specific to Jobvite and Reference Data (RDM) to Reltio — each maps to any object or custom field on the other side.
Employee Employee roster pushed through POST /employee (Onboard sync), used for referral matching and internal-mobility job postings. Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Employee is specific to Jobvite and Entities to Reltio — each maps to any object or custom field on the other side.
Attachment Resumes, cover letters, and files attached to a candidate; synced out to object storage or a document management system. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Attachment is specific to Jobvite and Relations to Reltio — each maps to any object or custom field on the other side.
Offer Offer state tied to an application (extended, accepted, declined); read out for offer-acceptance reporting and written to downstream comp or HR systems. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Offer is specific to Jobvite and Crosswalks to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Jobvite and Reltio

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Jobvite Reltio Sub-second propagation

DetectionJobvite notifies Stacksync of record changes through webhook events. A candidate hired webhook, configured per customer by a Jobvite rep, POSTs to a custom URL on hire/offer-accepted events.

DeliveryEach detected change is written to Reltio through its API, with automatic retries and rate-limit backoff.

Reltio Jobvite Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

DeliveryEach detected change is written to Jobvite through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Jobvite: Roughly 15 requests per minute and 850 per hour, reset at midnight Pacific, with per-endpoint daily caps (e.g. 20,000/day candidate GET/PUT, 500/day employee sync); 429 on exceed.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Jobvite ⇄ Reltio

Connect Jobvite and Reltio for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Jobvite–Reltio connection.

Real-time

Two-way sync

Changes in Jobvite or Reltio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Jobvite or Reltio data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Jobvite or Reltio record.

Observability

Monitoring

Track your Jobvite ⇄ Reltio sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Jobvite and Reltio.

How the Jobvite and Reltio connectors work

Jobvite

Integration surface
REST API (JSON) with candidate, requisition (job), and employee feed endpoints under https://api.jobvite.com/{version}
Authentication
API key (api) and secret (sc) plus company ID (companyId), sent in request headers since Jobvite's April 1, 2024 move from URL-query to header-based auth. Credentials are provisioned per customer by Jobvite Support.
Change detection
A candidate hired webhook, configured per customer by a Jobvite rep, POSTs to a custom URL on hire/offer-accepted events; otherwise Stacksync polls the candidate and job feeds on a schedule and diffs results, since records carry no per-item modified-date filter.
Capabilities
read · write · webhooks
Rate limits
Roughly 15 requests per minute and 850 per hour, reset at midnight Pacific, with per-endpoint daily caps (e.g. 20,000/day candidate GET/PUT, 500/day employee sync); 429 on exceed.
Jobvite setup guide

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

How to connect Jobvite to Reltio — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Jobvite and Reltio with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Jobvite connected
    Reltio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Jobvite and Reltio objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Jobvite ⇄ Reltio
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Jobvite Reltio
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Jobvite and Reltio integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 431 integrations available for Jobvite and Reltio.

Popular · 7 of 431
All Jobvite integrations All Reltio integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own