Skip to content
Database ⇄ Accounting and finance

OCI Database (Oracle Cloud) to Recurly integration — real-time, two-way sync

Keep OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) and Recurly

Work with Recurly's financial data straight from OCI Database (Oracle Cloud): 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 Invoices, Transactions, Line Items, Coupons and Redemptions from Recurly into Materialized views, Schemas, Sequences, PL/SQL procedures and packages in OCI Database (Oracle Cloud) and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against OCI Database (Oracle Cloud), 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 Run on-prem Oracle and OCI side by side during a cloud migration while keeping both ends writable.
  • 04 Expose ERP or billing data held in OCI to internal tools by syncing selected schemas to a managed Postgres.

Common sync patterns

Internal tools without API plumbing

Build dashboards and back-office tools directly on OCI Database (Oracle Cloud); Stacksync handles the API calls, rate limits, and retries against Recurly.

Write back safely

Updates written to the synced tables in OCI Database (Oracle Cloud) propagate into Recurly, so automations can create or correct finance records without custom integration code.

React to financial events

Changes in Recurly appear in OCI Database (Oracle Cloud) as row changes, so you can trigger downstream logic with the database tooling you already use.

What you can sync between OCI Database (Oracle Cloud) 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.

OCI Database (Oracle Cloud) objects Recurly objects How this pairing syncs
Tables The primary sync surface; rows are read and written directly over SQL 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. Tables is specific to OCI Database (Oracle Cloud) and Accounts to Recurly — each maps to any object or custom field on the other side.
Views Read-only projections used to expose curated subsets to downstream systems 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. Views is specific to OCI Database (Oracle Cloud) and Subscriptions to Recurly — each maps to any object or custom field on the other side.
Materialized views Precomputed result sets sometimes used as stable read sources for replication Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. Materialized views is specific to OCI Database (Oracle Cloud) and Plans to Recurly — each maps to any object or custom field on the other side.
Schemas Namespace boundaries that scope which objects a sync connection can access Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. Schemas is specific to OCI Database (Oracle Cloud) and Invoices to Recurly — each maps to any object or custom field on the other side.
Sequences Key generators that matter when writing new rows from external systems Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. Sequences is specific to OCI Database (Oracle Cloud) and Transactions to Recurly — each maps to any object or custom field on the other side.
PL/SQL procedures and packages Server-side logic that can react to synced data or transform it in place Line Items One-time charges and credits on an account outside a subscription; synced for accurate revenue and adjustment reporting. PL/SQL procedures and packages is specific to OCI Database (Oracle Cloud) and Line Items to Recurly — each maps to any object or custom field on the other side.

How changes propagate between OCI Database (Oracle Cloud) 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.

OCI Database (Oracle Cloud) Recurly Sub-second propagation

DetectionChanges in OCI Database (Oracle Cloud) are captured at the source via change data capture — no polling loop against its API. Log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling.

DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.

Recurly OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • OCI Database (Oracle Cloud): Throughput bounded by instance sizing rather than API quotas.
  • 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 OCI Database (Oracle Cloud) ⇄ Recurly

Connect OCI Database (Oracle Cloud) and Recurly for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every OCI Database (Oracle Cloud)–Recurly connection.

Real-time

Two-way sync

Changes in OCI Database (Oracle Cloud) or Recurly instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) or Recurly record.

Observability

Monitoring

Track your OCI Database (Oracle Cloud) ⇄ Recurly sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between OCI Database (Oracle Cloud) and Recurly.

How the OCI Database (Oracle Cloud) and Recurly connectors work

OCI Database (Oracle Cloud)

Integration surface
SQL wire protocol (Oracle Net) via JDBC, ODBC, and native drivers; ORDS REST optionally exposes tables over HTTP
Authentication
database credentials, commonly with mutual TLS using a client wallet on Autonomous Database; OCI IAM integration available
Change detection
log-based CDC from redo logs (LogMiner or GoldenGate), or timestamp polling
Capabilities
read · write · CDC
Rate limits
throughput bounded by instance sizing rather than API quotas

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 OCI Database (Oracle Cloud) 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 OCI Database (Oracle Cloud) 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
    OCI Database (Oracle Cloud) connected
    Recurly connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the OCI Database (Oracle Cloud) 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 · OCI Database (Oracle Cloud) ⇄ 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
    OCI Database (Oracle Cloud) Recurly
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

OCI Database (Oracle Cloud) 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
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

Related integrations

Every pair below is a real-time, two-way sync. Search all 429 integrations available for OCI Database (Oracle Cloud) and Recurly.

Popular · 7 of 429
All OCI Database (Oracle Cloud) 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