Skip to content
E-commerce ⇄ Database

Easypost to Reltio integration — real-time, two-way sync

Keep Easypost and Reltio 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 Easypost and Reltio

Give your engineers Easypost's products, orders, and customers in Reltio: read them with normal queries, write inventory and prices back through the sync, and skip the storefront API.

E-commerce data sits behind an API built for the storefront, not for your internal systems. Teams that need those records, for order routing, inventory logic, reporting, or back-office tools, end up writing integration code against a rate-limited API and maintaining it through every catalog change and platform upgrade.

Stacksync mirrors Rate, Tracker, Batch, CarrierAccount from Easypost into Reltio and keeps both sides consistent in real time. Whatever Easypost holds, whether products, orders, customers, or inventory, those records become rows your code can query, and changes written in Reltio, such as new prices, stock levels, or fulfillment status, sync back into Easypost with its validations respected.

Merchandising and operations keep working in the storefront, engineers keep working in the database, and neither side has to reconcile against a nightly export.

Common use cases

  • 01 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 02 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.
  • 03 Pull Shipment, Rate, and Refund records into a warehouse to report shipping cost per carrier and service and reclaim postage on labels that were never scanned.
  • 04 Batch-create and buy labels for a day's orders, generate a ScanForm, and write each label and tracking code back into the fulfillment system.

Common sync patterns

Controlled write-back

Choose exactly which tables and fields may flow from Reltio back into Easypost, keeping the store authoritative on what it owns.

Read the store's data with a query

Records from Easypost, whether products, orders, customers, or inventory, live in Reltio as ordinary tables or collections, joinable with the rest of your data.

Internal tools and automations without API code

Scripts and services read and write the synced tables; Stacksync handles the Easypost API, rate limits, and retries.

What you can sync between Easypost and Reltio

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 Reltio objects How this pairing syncs
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. Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Shipment is specific to Easypost and Entities to Reltio — each maps to any object or custom field on the other side.
Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Address is specific to Easypost and Relations to Reltio — each maps to any object or custom field on the other side.
Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Parcel is specific to Easypost and Crosswalks to Reltio — each maps to any object or custom field on the other side.
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. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Rate is specific to Easypost and Interactions to Reltio — 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. Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Tracker is specific to Easypost and Matches (Potential Matches) to Reltio — 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. Activity Log Immutable audit trail of changes to entities and relations via /activities; read-only, used for history, lineage, and compliance reporting. Batch is specific to Easypost and Activity Log to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Easypost and Reltio

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.

Easypost Reltio Sub-second propagation

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 Reltio through its API, with automatic retries and rate-limit backoff.

Reltio Easypost Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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

Rate-limit considerations

  • Easypost: Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Easypost ⇄ Reltio

Connect Easypost and Reltio for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Easypost–Reltio connection.

Real-time

Two-way sync

Changes in Easypost or Reltio instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Easypost or Reltio 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 Easypost or Reltio record.

Observability

Monitoring

Track your Easypost ⇄ Reltio sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Easypost and Reltio.

How the Easypost and Reltio connectors work

Easypost

Integration surface
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
Change detection
Webhooks deliver an Event via HTTP POST on object changes (e.g. tracker.updated); historical pulls via list/index endpoints using before_id/after_id cursor pagination
Capabilities
read · write · webhooks
Rate limits
Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests
Easypost setup guide

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

How to connect Easypost to Reltio — 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 Easypost and Reltio 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
    Easypost connected
    Reltio connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Easypost and Reltio 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 · Easypost ⇄ Reltio
    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
    Easypost Reltio
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Easypost and Reltio 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
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 389 integrations available for Easypost and Reltio.

Popular · 6 of 389
All Easypost integrations All Reltio 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