Real-time
Two-way sync
Changes in Recurly or Treasuredata instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Analytics
Recurly to Treasuredata integration — real-time, two-way sync
Keep Recurly and Treasuredata 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 Treasuredata
Feed the customers, invoices, and revenue records in Recurly into Treasuredata in real time, so dashboards and reports run on current numbers instead of last night's export.
Recurly holds the financial truth: who the customers are, what they were invoiced, what they paid, and what revenue landed. Treasuredata is where that data is turned into dashboards, reports, and metrics, but it only reflects the world as of its last load. When the connection between them is a scheduled extract or a hand-built pipeline, analysis runs a step behind the books, and the numbers on a chart rarely match the numbers in the finance system.
Stacksync keeps Accounts, Subscriptions, Plans, Invoices in Recurly in sync with Query Jobs, Databases, Tables, Master (Parent) Segments in Treasuredata, field by field and in real time. A customer, invoice, or amount created or corrected in Recurly shows up in Treasuredata within seconds, mapped to the right record. Where Treasuredata keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Treasuredata already tracks.
There is no middleware to build, no API rate limits to babysit, and no nightly job that leaves the morning's reporting running on yesterday's figures.
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 Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
- 04 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
Common sync patterns
Where Treasuredata keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Recurly attaches to the matching account or user in Treasuredata, so segments and cohorts can be cut by real financial standing.
Financial records land in Treasuredata for reporting
Invoices, payments, and revenue from Recurly flow into Treasuredata as they change, so dashboards are built on live figures rather than a periodic extract.
One customer key across both
A customer or account in Recurly is matched to the corresponding record in Treasuredata, so financial numbers join cleanly to whatever Treasuredata already reports on.
What you can sync between Recurly and Treasuredata
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 | Treasuredata objects | How this pairing syncs | |
|---|---|---|---|
| Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. | Scheduled Queries Cron-scheduled Presto/Trino (or Hive) jobs that materialize results into result tables; Stacksync reads those materialized tables downstream. | Line Items is specific to Recurly and Scheduled Queries to Treasuredata — each maps to any object or custom field on the other side. | |
| Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. | Coupons and Redemptions is specific to Recurly and Query Jobs to Treasuredata — each maps to any object or custom field on the other side. | |
| 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). | Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. | Billing Info is specific to Recurly and Databases to Treasuredata — each maps to any object or custom field on the other side. | |
| Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. | Measured Units and Usage is specific to Recurly and Tables to Treasuredata — each maps to any object or custom field on the other side. | |
| 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. | Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. | Accounts is specific to Recurly and Master (Parent) Segments to Treasuredata — 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. | Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. | Subscriptions is specific to Recurly and Segments to Treasuredata — each maps to any object or custom field on the other side. |
How changes propagate between Recurly and Treasuredata
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 Treasuredata 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 Treasuredata through its API, with automatic retries and rate-limit backoff.
Treasuredata Recurly Interval-based propagation
DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.
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.
- Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Recurly ⇄ Treasuredata
Connect Recurly and Treasuredata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–Treasuredata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Recurly or Treasuredata 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 Treasuredata record.
Observability
Monitoring
Track your Recurly ⇄ Treasuredata 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 Treasuredata.
How the Recurly and Treasuredata 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.
Treasuredata
- Integration surface
- TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
- Authentication
- API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
- Change detection
- Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
- Capabilities
- read · write
- Rate limits
- TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works
How to connect Recurly to Treasuredata — 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 Treasuredata 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
Treasuredata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Recurly and Treasuredata 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 ⇄ TreasuredataCustomers 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 TreasuredataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Recurly and Treasuredata integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Recurly and Treasuredata: authenticate both systems, choose the objects to sync (such as Recurly's Line Items and Coupons and Redemptions), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Recurly and Treasuredata: Where Treasuredata keeps account or user records: finance attributes enrich them; Financial records land in Treasuredata for reporting; One customer key across both. Status, plan, or outstanding balance from Recurly attaches to the matching account or user in Treasuredata, so segments and cohorts can be cut by real financial standing.
-
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. Treasuredata: TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys. Authentication: API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints). 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. Treasuredata: Queries run as asynchronous jobs on Presto/Trino or Hive; large reads and exports are pulled from job results rather than a single synchronous response. Stacksync's field mapping accounts for these differences between Recurly and Treasuredata 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 Treasuredata 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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 375 integrations available for Recurly and Treasuredata.
Popular · 5 of 375
No integrations match .
