Skip to content
Database ⇄ Human resources

InterSystems IRIS to Jobvite integration — real-time, two-way sync

Keep InterSystems IRIS and Jobvite 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 InterSystems IRIS and Jobvite

Put your workforce data where your apps can reach it: InterSystems IRIS 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. InterSystems IRIS is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Candidate, Requisition (Job), Application, Workflow Status in Jobvite need to exist as queryable Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS 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 Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS with Candidate, Requisition (Job), Application, Workflow Status 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 Write enriched or corrected records from SaaS apps back into IRIS tables for on-platform processing
  • 02 Replicate IRIS tables to Postgres so application teams can build against a familiar database
  • 03 Write New Hire records into an HRIS or onboarding system the moment a candidate is marked hired, driven by Jobvite's candidate hired webhook.
  • 04 Push headcount-approved Requisitions from an internal planning database into Jobvite via POST /job so approved roles post to the career site automatically.

Common sync patterns

Computed and operational fields flow back

Values assembled or corrected in InterSystems IRIS 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 Persistent Classes, Globals, Namespaces, Stored Procedures in InterSystems IRIS, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between InterSystems IRIS and Jobvite

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.

InterSystems IRIS objects Jobvite objects How this pairing syncs
Tables Relational projections of stored data are the primary read/write surface for SQL-based syncs. Attachment Resumes, cover letters, and files attached to a candidate; synced out to object storage or a document management system. Tables is specific to InterSystems IRIS and Attachment to Jobvite — each maps to any object or custom field on the other side.
Views SQL views expose curated slices of data for outbound replication. Offer Offer state tied to an application (extended, accepted, declined); read out for offer-acceptance reporting and written to downstream comp or HR systems. Views is specific to InterSystems IRIS and Offer to Jobvite — each maps to any object or custom field on the other side.
Schemas Schema organization scopes which tables a sync connection can see. Candidate Read from the candidate feed (GET /candidate) and written back via POST /candidate/updateCandidates to change status, notes, and disposition on each record. Schemas is specific to InterSystems IRIS and Candidate to Jobvite — each maps to any object or custom field on the other side.
Persistent Classes Object-model classes project to tables, so class data is reachable through SQL. Requisition (Job) Job openings created or updated through POST /job and read from GET /jobFeed; maps to opening tables in an ATS reporting warehouse. Persistent Classes is specific to InterSystems IRIS and Requisition (Job) to Jobvite — each maps to any object or custom field on the other side.
Globals The underlying multidimensional storage; typically accessed indirectly via SQL or objects in 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. Globals is specific to InterSystems IRIS and Application to Jobvite — each maps to any object or custom field on the other side.
Namespaces Namespaces partition databases and determine the connection context for integrations. Workflow Status The pipeline stage per application (Screen, Interview, Offer, Hired); updated through POST /candidate/updateCandidates to advance records. Namespaces is specific to InterSystems IRIS and Workflow Status to Jobvite — each maps to any object or custom field on the other side.

How changes propagate between InterSystems IRIS and Jobvite

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.

InterSystems IRIS Jobvite Interval-based propagation

DetectionStacksync polls InterSystems IRIS for changes on an incremental schedule, reading only records changed since the previous pass. Polling (timestamp or query-based).

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

Jobvite InterSystems IRIS 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 applied to InterSystems IRIS as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • InterSystems IRIS: Constrained by database resources rather than published API rate limits.
  • 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.
What ships with InterSystems IRIS ⇄ Jobvite

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever InterSystems IRIS or Jobvite 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 InterSystems IRIS or Jobvite record.

Observability

Monitoring

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

Trading partners

EDI

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

How the InterSystems IRIS and Jobvite connectors work

InterSystems IRIS

Integration surface
SQL over JDBC/ODBC, plus object and REST access layers
Authentication
Database credentials
Change detection
Polling (timestamp or query-based); no standard webhook surface
Capabilities
read · write
Rate limits
Constrained by database resources rather than published API rate limits

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
How it works

How to connect InterSystems IRIS to Jobvite — 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 InterSystems IRIS and Jobvite 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
    InterSystems IRIS connected
    Jobvite connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the InterSystems IRIS and Jobvite 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 · InterSystems IRIS ⇄ Jobvite
    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
    InterSystems IRIS Jobvite
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

InterSystems IRIS and Jobvite 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 467 integrations available for InterSystems IRIS and Jobvite.

Popular · 8 of 467
All InterSystems IRIS integrations All Jobvite 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