Two-way sync
Changes in Jobvite or Rillet instantly reflect in both systems. No stale data, no manual imports.
Keep Jobvite and Rillet in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Rillet runs the money side of the company: who gets paid, what it costs, and which part of the business the cost belongs to. Jobvite runs the people side: who works here, which team they sit in, and how their employment changes over time. The two overlap on the same people and the same org structure, because every employee is also a payee and every department is also a cost center. When that overlap is maintained by hand, a new hire, a transfer, or a termination has to be keyed twice, and the two systems start to disagree about who is active and where the cost lands.
Stacksync syncs Invoice, Credit Memo, Bill, Journal Entry in Rillet with Application, Workflow Status, New Hire, Employee in Jobvite bi-directionally and in real time. A person added, updated, or deactivated on either side appears on the other within seconds, with field-level mapping and conflict resolution in place of CSV exports and nightly batch jobs.
That matters most when money follows a people event. A hire that finance can pay, a leaver whose access ends, a transfer that redirects cost to the right team, all happen from one change instead of two, so headcount and spend reconcile from the same set of records.
A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.
The org structure maintained in Jobvite keeps the departments or cost centers in Rillet current, so spend and headcount roll up the same way.
A role, department, or employment-status change in either system updates the other within seconds, so cost allocation, access, and reporting reflect the current state.
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 | Rillet objects | How this pairing syncs | |
|---|---|---|---|
| Attachment Resumes, cover letters, and files attached to a candidate; synced out to object storage or a document management system. | Invoice Payment Synced with incremental and full sync per the Stacksync docs. | Attachment is specific to Jobvite and Invoice Payment to Rillet — 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. | Charge Synced with incremental and full sync per the Stacksync docs. | Offer is specific to Jobvite and Charge to Rillet — each maps to any object or custom field on the other side. | |
| Candidate Read from the candidate feed (GET /candidate) and written back via POST /candidate/updateCandidates to change status, notes, and disposition on each record. | Reimbursement Synced with incremental and full sync per the Stacksync docs. | Candidate is specific to Jobvite and Reimbursement to Rillet — each maps to any object or custom field on the other side. | |
| Requisition (Job) Job openings created or updated through POST /job and read from GET /jobFeed; maps to opening tables in an ATS reporting warehouse. | Custom Field Synced with incremental and full sync per the Stacksync docs. | Requisition (Job) is specific to Jobvite and Custom Field to Rillet — each maps to any object or custom field on the other side. | |
| Application Links a candidate to one requisition with its workflow state; read for pipeline reporting and status written back through the candidate update call. | Account Synced with incremental and full sync per the Stacksync docs. | Application is specific to Jobvite and Account to Rillet — 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. | Customer Synced with incremental and full sync per the Stacksync docs. | Workflow Status is specific to Jobvite and Customer to Rillet — each maps to any object or custom field on the other side. |
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.
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 Rillet through its API, with automatic retries and rate-limit backoff.
DetectionRillet pushes changes as they happen — webhook events backed by change data capture. Near real-time updates via change tracking.
DeliveryEach detected change is written to Jobvite through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Jobvite–Rillet connection.
Changes in Jobvite or Rillet instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Jobvite or Rillet data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Jobvite or Rillet record.
Track your Jobvite ⇄ Rillet sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Jobvite and Rillet.
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.
Authenticate Jobvite and Rillet with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Jobvite and Rillet 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Jobvite and Rillet: authenticate both systems, choose the objects to sync (such as Jobvite's Attachment and Offer), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Jobvite and Rillet: One employee identity; Department and cost-center alignment; Status changes propagate. A person's name, ID, or contact details corrected in either system update the other, so finance and HR reference the same person instead of maintaining two versions.
Jobvite: 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. Rillet: REST API (OpenAPI-specified, with production and sandbox environments). Authentication: API key generated in Rillet (Organization Setting -> API Access); uncheck Read Only for bidirectional sync, check Read Only for one-way sync. Stacksync manages authentication, retries, and rate limits on both sides.
Rillet: Several objects (Subsidiary, Tax Rate, Product, Contract, Bank Account, Bank Transaction) do not support incremental sync — historic sync only. Jobvite: Candidate writes go through POST /candidate/updateCandidates rather than per-field PATCH, so status and disposition changes are submitted as candidate update payloads. Stacksync's field mapping accounts for these differences between Jobvite and Rillet without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Jobvite and Rillet records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Jobvite and Rillet connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Jobvite–Rillet integration in-house.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 427 integrations available for Jobvite and Rillet.