Skip to content
Accounting and finance

Connect Recurly to any app with two-way sync.

Two-way sync Recurly across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Recurly.

These objects sync between Recurly and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Recurly exposes them.

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.
Subscriptions
Recurring subscription records tied to an Account and a Plan, with state, term, and next-bill date. Core object, synced two-way to drive provisioning and reporting.
Plans
The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database.
Invoices
Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges.
Transactions
Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis.
Line Items
One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting.
Coupons and Redemptions
Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis.
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).
Measured Units and Usage
Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing.
API surface

How Stacksync connects to Recurly.

The connector runs on Recurly's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
What ships with Recurly

Connect Recurly for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Recurly instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Recurly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Recurly connector.

Recurly is the subscription-billing and recurring-revenue system of record, owned by finance and billing operations with RevOps and engineering support. Accounts, Subscriptions, Plans, Invoices, Transactions, and Billing Info live here as the authoritative record of who is subscribed to what, at what price, and their payment state. It drives MRR, churn, dunning, and revenue recognition, so finance, product, and go-to-market teams all need to read subscription state and write account and plan changes back.

  • Finance and billing operations
  • RevOps
  • Revenue accounting
  • Data engineering
  • Subscription operations managers

  1. Sync Accounts and Subscriptions bi-directionally with Postgres so product and provisioning systems read live entitlement state and write plan or seat changes back to Recurly.

  2. Stream Invoices, Transactions, and Credit Payments into a Snowflake or BigQuery warehouse for MRR, churn, and dunning dashboards without manual CSV exports.

  3. Mirror Recurly Accounts and subscription status onto Salesforce Accounts so CSMs and reps see billing and renewal health on the record.

  4. Trigger revenue-recognition or ERP entries when new_subscription and canceled_subscription webhooks fire.

  5. Post usage records to Measured Units on metered Subscriptions from a metering database before each bill run.

  6. Two-way sync of Accounts and Subscriptions with an operational Postgres database so product provisioning reads live entitlement and plan state while subscription and account changes flow back to Recurly.

All Recurly integrations

Pick the system you need to keep in sync with Recurly. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 41

ERP · 37

Database · 50

Data warehouse · 28

Business productivity · 37

Accounting and finance · 16

How it works

Set up Recurly in minutes, without APIs.

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 Recurly with its 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
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Recurly objects to sync — Stacksync auto-detects the schema, 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 · 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
    Recurly database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Recurly connector FAQ

What can I sync with the Recurly connector?

Recurly's core objects — Accounts, Subscriptions, Plans, Invoices and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Recurly?

Via REST API (V3, date-versioned; legacy V2 XML API also exists), authenticated with API key via HTTP Basic auth (key as username, blank password); keys are per-site, with separate sandbox and production keys. Changes are detected as follows — 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. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Recurly connector two-way?

Yes. Changes made in Recurly propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does a Recurly integration take to set up?

Most Recurly integrations go live in minutes: authenticate Recurly and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Recurly data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Recurly data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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
CSA STAR
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
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