Real-time
Two-way sync
Changes in Recurly or TiDB instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Database
Recurly to TiDB integration — real-time, two-way sync
Keep Recurly and TiDB 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 Recurly and TiDB
Work with Recurly's financial data straight from TiDB: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.
Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.
Stacksync mirrors Accounts, Subscriptions, Plans, Invoices from Recurly into Columns, Indexes, Sequences, Databases in TiDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against TiDB, and rows your code writes or updates flow back into Recurly with validation, so the finance system stays the system of record.
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 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
- 04 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
Common sync patterns
Internal tools without API plumbing
Build dashboards and back-office tools directly on TiDB; Stacksync handles the API calls, rate limits, and retries against Recurly.
Write back safely
Updates written to the synced tables in TiDB propagate into Recurly, so automations can create or correct finance records without custom integration code.
React to financial events
Changes in Recurly appear in TiDB as row changes, so you can trigger downstream logic with the database tooling you already use.
What you can sync between Recurly and TiDB
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.
| Recurly objects | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Accounts is specific to Recurly and Databases to TiDB — each maps to any object or custom field on the other side. | |
| 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. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Subscriptions is specific to Recurly and Tables to TiDB — each maps to any object or custom field on the other side. | |
| Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | Views Logical views for shaping reads before syncing outward. | Plans is specific to Recurly and Views to TiDB — each maps to any object or custom field on the other side. | |
| Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Columns MySQL-compatible types mapped to fields in the paired system. | Invoices is specific to Recurly and Columns to TiDB — each maps to any object or custom field on the other side. | |
| Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Indexes Secondary indexes that keep incremental sync queries efficient. | Transactions is specific to Recurly and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Sequences Server-side ID generation relevant when external systems write rows. | Line Items is specific to Recurly and Sequences to TiDB — each maps to any object or custom field on the other side. |
How changes propagate between Recurly and TiDB
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.
Recurly TiDB 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 applied to TiDB as a row-level write, with types converted between the two schemas.
TiDB Recurly Sub-second propagation
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- 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.
- TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Recurly ⇄ TiDB
Connect Recurly and TiDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–TiDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Recurly or TiDB 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 or TiDB record.
Observability
Monitoring
Track your Recurly ⇄ TiDB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Recurly and TiDB.
How the Recurly and TiDB connectors work
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.
TiDB
- Integration surface
- MySQL wire protocol (SQL)
- Authentication
- Database credentials (MySQL-compatible username/password)
- Change detection
- Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
- Capabilities
- read · write · CDC
- Rate limits
- Throughput scales with cluster size rather than fixed API quotas
How it works
How to connect Recurly to TiDB — 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.
- 01
Connect your apps
Authenticate Recurly and TiDB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Recurly
connected
TiDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Recurly and TiDB 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.
objects · Recurly ⇄ TiDBCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Recurly TiDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Recurly and TiDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Recurly and TiDB: authenticate both systems, choose the objects to sync (such as Recurly's Accounts and Subscriptions), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Recurly: 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. TiDB: MySQL wire protocol (SQL). Authentication: Database credentials (MySQL-compatible username/password). Stacksync manages authentication, retries, and rate limits on both sides.
-
Recurly: Rate limits default to 1,000 requests/min on production (only GET requests count) and 400/min on sandbox (all requests count), measured over a sliding 5-minute window; breaches return HTTP 429. TiDB: Storage and compute scale horizontally by adding TiKV and TiDB nodes rather than resizing a single server. Stacksync's field mapping accounts for these differences between Recurly and TiDB 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 Recurly and TiDB records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Recurly and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Recurly–TiDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Recurly and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 424 integrations available for Recurly and TiDB.
Popular · 8 of 424
-
Recurly ⇄ TimescaleDB -
Recurly ⇄ VoltDB -
Recurly ⇄ YugabyteDB -
Recurly ⇄ Amazon DynamoDB -
TiDB ⇄ QuickBooks -
TiDB ⇄ Stripe -
TiDB ⇄ Coupa -
TiDB ⇄ Zuora
No integrations match .
