Skip to content
Human resources ⇄ Accounting and finance

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

Keep Jobvite and Recurly 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 Recurly

Keep the employee, department, and cost records that Recurly and Jobvite share consistent in real time, so the finance system and the people system stop drifting apart.

Recurly 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 Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly with Requisition (Job), Application, Workflow Status, New Hire 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.

Common use cases

  • 01 Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.
  • 02 Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.
  • 03 Push headcount-approved Requisitions from an internal planning database into Jobvite via POST /job so approved roles post to the career site automatically.
  • 04 Consolidate Applications, Offers, and Workflow Status into a warehouse for time-to-fill and funnel reporting across every requisition.

Common sync patterns

New person becomes a known record in finance

When someone is added in Jobvite, a matching employee or payee record appears in Recurly, ready for payroll, expenses, or cost allocation without anyone rekeying the details.

One employee identity

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.

Department and cost-center alignment

The org structure maintained in Jobvite keeps the departments or cost centers in Recurly current, so spend and headcount roll up the same way.

What you can sync between Jobvite and Recurly

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 Recurly objects How this pairing syncs
Candidate Read from the candidate feed (GET /candidate) and written back via POST /candidate/updateCandidates to change status, notes, and disposition on each record. Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Candidate is specific to Jobvite and Transactions to Recurly — 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. Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. Requisition (Job) is specific to Jobvite and Line Items to Recurly — 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. Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. Application is specific to Jobvite and Coupons and Redemptions to Recurly — 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. Billing Info Tokenized payment method (card/ACH) on an account; written when onboarding customers and read for payment-health signals (never stores raw card numbers). Workflow Status is specific to Jobvite and Billing Info to Recurly — 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. Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. New Hire is specific to Jobvite and Measured Units and Usage to Recurly — 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. Accounts Customer/billing entity records keyed by account_code; the anchor most subscriptions and invoices hang off. Synced two-way with CRM accounts or a customer database. Employee is specific to Jobvite and Accounts to Recurly — each maps to any object or custom field on the other side.

How changes propagate between Jobvite and Recurly

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 Recurly 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 Recurly through its API, with automatic retries and rate-limit backoff.

Recurly Jobvite Sub-second propagation

DetectionRecurly notifies Stacksync of record changes through webhook events. Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints.

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.
  • Recurly: Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
What ships with Jobvite ⇄ Recurly

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Jobvite ⇄ Recurly 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 Recurly.

How the Jobvite and Recurly 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

Recurly

Integration surface
REST API (V3, date-versioned; legacy V2 XML API also exists)
Authentication
API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys
Change detection
Webhooks (JSON or XML, one format per endpoint) for account, subscription, payment, and invoice events, plus incremental polling of list endpoints sorted by updated_at with begin_time/end_time filters
Capabilities
read · write · webhooks
Rate limits
Production sites default to 1,000 requests/min with only GET requests counting toward the limit; sandbox sites 400/min with all requests counting; the limit is a sliding 5-minute window, X-RateLimit headers report the quota, and breaches return HTTP 429.
How it works

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

    Choose tables

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

Jobvite and Recurly 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 501 integrations available for Jobvite and Recurly.

Popular · 8 of 501
All Jobvite integrations All Recurly 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