Two-way sync
Changes in Easypost or Recurly instantly reflect in both systems. No stale data, no manual imports.
Keep Easypost 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.
Easypost runs the storefront — the catalog, the orders, and the buyers placing them. Recurly records the money behind those orders — invoices, revenue, payments, and the ledger the business closes on. The overlap is every customer, order, and product both sides need to agree on, and when that overlap is bridged by CSV export or an overnight batch, finance reconciles against stale numbers while the store quotes prices or stock the books no longer recognize.
Stacksync syncs Plans, Invoices, Transactions, Line Items in Recurly with CarrierAccount, Webhook, Shipment, Address in Easypost field by field, in real time, and in both directions. You decide which system owns which fields — an order's totals from Easypost, its paid-or-overdue state from Recurly — and Stacksync keeps every copy consistent and resolves conflicts by the rules you set.
The result is one shared record of who bought what and whether it has been paid, so the storefront, support, and the finance team all read from the same current data instead of re-keying it between systems.
Products, SKUs, and prices maintained on one side propagate to the other, so what the store sells and what the ledger books stay in step.
Refunds, cancellations, and credit notes raised in either system update the corresponding record in the other, keeping balances honest on both sides.
A new or updated order in Easypost creates or updates the matching invoice or revenue record in Recurly, so billing and reporting start without re-entry.
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.
| Easypost objects | Recurly objects | How this pairing syncs | |
|---|---|---|---|
| Rate Carrier service and price options EasyPost generates on a Shipment; read-only - you select a rate id and buy it, you do not create or edit rates directly. | Measured Units and Usage Metered-billing units; usage records are posted to a subscription before each bill run for consumption-based pricing. | Rate is specific to Easypost and Measured Units and Usage to Recurly — each maps to any object or custom field on the other side. | |
| Tracker Tracking for a shipment by tracking_code and carrier; create a Tracker to begin tracking, read status and tracking_details, and receive tracker.updated events via webhook as the parcel moves. | 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. | Tracker is specific to Easypost and Accounts to Recurly — each maps to any object or custom field on the other side. | |
| Batch Bulk shipment processing; create a batch, add or remove shipments, buy all labels at once, and generate a consolidated label or ScanForm for the day's orders. | 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. | Batch is specific to Easypost and Subscriptions to Recurly — each maps to any object or custom field on the other side. | |
| CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. | Plans The product and pricing catalog (plan codes, intervals, add-ons); usually mastered in Recurly and read out, or mirrored from a product database. | CarrierAccount is specific to Easypost and Plans to Recurly — each maps to any object or custom field on the other side. | |
| Webhook Event subscriptions delivering an Event via HTTP POST on object changes; full CRUD (create, retrieve, list, update, delete) and the mechanism for near-real-time change delivery to Stacksync. | Invoices Charge and credit billing documents; read-heavy for revenue reporting, and creatable through Purchases for one-off charges. | Webhook is specific to Easypost and Invoices to Recurly — each maps to any object or custom field on the other side. | |
| Shipment The central writable object: create with a to/from Address and Parcel, receive Rate options, then buy a label to get postage_label and tracking_code; retrieve and list with cursor pagination. | Transactions Individual payment attempts — captures, refunds, and voids; typically read into a warehouse for reconciliation and dunning analysis. | Shipment is specific to Easypost and Transactions to Recurly — each maps to any object or custom field on the other side. |
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.
DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.
DeliveryEach detected change is written to Recurly through its API, with automatic retries and rate-limit backoff.
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 Easypost through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Easypost–Recurly connection.
Changes in Easypost or Recurly instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Easypost or Recurly data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Easypost or Recurly record.
Track your Easypost ⇄ Recurly sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Easypost and Recurly.
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.
Authenticate Easypost 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.
Pick the Easypost 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Easypost and Recurly: authenticate both systems, choose the objects to sync (such as Easypost's Rate and Tracker), map fields visually, and changes propagate both ways in milliseconds — no code required.
Easypost: REST API (EasyPost API v2, https://api.easypost.com/v2). Authentication: HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys. 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. 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. Easypost: Test and Production API keys are separate: test-mode calls do not create real labels or charges, so integration tests and dry-run backfills should run against the test key before touching production. Stacksync's field mapping accounts for these differences between Easypost and Recurly 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 Easypost and Recurly records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Easypost and Recurly connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Easypost–Recurly integration in-house.
Yes — Stacksync ships production-grade connectors for both Easypost and Recurly. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 459 integrations available for Easypost and Recurly.