Real-time
Two-way sync
Changes in Recurly or Splunk instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ Analytics
Recurly to Splunk integration — real-time, two-way sync
Keep Recurly and Splunk 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 Splunk
Feed the customers, invoices, and revenue records in Recurly into Splunk 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. Splunk 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 Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts in Recurly in sync with Users and Roles, Dashboards, Search Results, Saved Searches in Splunk, field by field and in real time. A customer, invoice, or amount created or corrected in Recurly shows up in Splunk within seconds, mapped to the right record. Where Splunk keeps its own accounts or users, the flow runs both ways, so finance attributes can enrich what Splunk 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 Export Users and Roles into an IAM database for periodic access reviews, or provision them from an identity source of truth.
- 04 Sync fired-alert history and saved-search definitions into Postgres so security and reliability teams query alert trends and detection coverage in SQL.
Common sync patterns
Revenue alongside the rest of the data
The amounts Recurly records sit next to product, usage, or operational data in Splunk, so a single view combines what was billed with what actually happened.
Reports refresh as the books change
Instead of waiting for a scheduled load, Splunk updates the moment a figure moves in Recurly, so a dashboard opened at any point in the day is current.
Where Splunk keeps account or user records: finance attributes enrich them
Status, plan, or outstanding balance from Recurly attaches to the matching account or user in Splunk, so segments and cohorts can be cut by real financial standing.
What you can sync between Recurly and Splunk
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 | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Coupons and Redemptions Discount definitions and their application to accounts and subscriptions; read for discount and promotion analysis. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | Coupons and Redemptions is specific to Recurly and Users and Roles to Splunk — 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). | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Billing Info is specific to Recurly and Dashboards to Splunk — 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. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Measured Units and Usage is specific to Recurly and Search Results to Splunk — 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. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Accounts is specific to Recurly and Saved Searches to Splunk — 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. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Subscriptions is specific to Recurly and Fired Alerts to Splunk — 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. | KV Store Collections App-scoped, MongoDB-backed key-value collections at /servicesNS/{owner}/{app}/storage/collections/data/{collection} with full CRUD and batch endpoints. Genuinely bidirectional lookup/state store — read records out or write records in. | Plans is specific to Recurly and KV Store Collections to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Recurly and Splunk
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 Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Recurly Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
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.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Recurly ⇄ Splunk
Connect Recurly and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Recurly–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Recurly or Splunk 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 Splunk record.
Observability
Monitoring
Track your Recurly ⇄ Splunk 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 Splunk.
How the Recurly and Splunk 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.
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Recurly to Splunk — 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 Splunk 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
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Recurly and Splunk 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 ⇄ SplunkCustomers 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 SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Recurly and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Recurly and Splunk: authenticate both systems, choose the objects to sync (such as Recurly's Coupons and Redemptions and Billing Info), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Splunk records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Recurly and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Recurly–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Recurly and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Recurly: 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. On Splunk: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Recurly side: Coupons and Redemptions, Billing Info, Measured Units and Usage, Accounts, plus custom fields where Recurly exposes them. On the Splunk side: Users and Roles, Dashboards, Search Results, Saved Searches. Stacksync auto-detects both schemas and converts types between the two systems.
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 473 integrations available for Recurly and Splunk.
Popular · 6 of 473
-
Recurly ⇄ Pendo -
Recurly ⇄ Treasuredata -
Splunk ⇄ Braintree -
Splunk ⇄ Navan -
Splunk ⇄ Ramp -
Splunk ⇄ Rillet
No integrations match .
