Two-way sync
Changes in Easypost or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Keep Easypost and Scaleway Postgres in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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 Tracker, Batch, CarrierAccount, Webhook from Easypost into Scaleway Postgres 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 Scaleway Postgres, 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.
Updates in Easypost arrive as row changes in Scaleway Postgres, so jobs and triggers can respond the moment an order, price, or stock level changes.
Prices, stock levels, or product details maintained in Scaleway Postgres sync back onto Easypost, so the storefront shows what your systems treat as true.
Orders and their status become rows in Scaleway Postgres for routing, fulfillment, and reporting, without polling the platform.
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 | Scaleway Postgres objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Tables Primary sync unit; each table maps to an object or table on the other side of the sync. | Address is specific to Easypost and Tables to Scaleway Postgres — 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. | Views Read-only sources for shaping data before it leaves the database. | Parcel is specific to Easypost and Views to Scaleway Postgres — 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. | Materialized views Precomputed result sets that can be read on a schedule for downstream syncs. | Rate is specific to Easypost and Materialized views to Scaleway Postgres — 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. | Schemas Namespace tables so multiple applications or environments can be synced selectively. | Tracker is specific to Easypost and Schemas to Scaleway Postgres — 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. | Sequences Generate primary keys; sync tooling must respect them when writing rows. | Batch is specific to Easypost and Sequences to Scaleway Postgres — 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. | Columns Postgres-native types, including JSONB and arrays, are mapped to fields in the paired system. | CarrierAccount is specific to Easypost and Columns to Scaleway Postgres — 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 applied to Scaleway Postgres as a row-level write, with types converted between the two schemas.
DetectionChanges in Scaleway Postgres are captured at the source via change data capture — no polling loop against its API. Log-based CDC via PostgreSQL logical replication where the managed instance permits it.
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–Scaleway Postgres connection.
Changes in Easypost or Scaleway Postgres instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Easypost or Scaleway Postgres 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 Scaleway Postgres record.
Track your Easypost ⇄ Scaleway Postgres sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Easypost and Scaleway Postgres.
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 Scaleway Postgres 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 Scaleway Postgres 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 Scaleway Postgres: authenticate both systems, choose the objects to sync (such as Easypost's Address and Parcel), map fields visually, and changes propagate both ways in milliseconds — no code required.
Scaleway Postgres: It runs the standard PostgreSQL engine, so ordinary Postgres drivers, ORMs, and SQL tooling work unmodified; managed-service restrictions apply to some server-level features. 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 Scaleway Postgres 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 Scaleway Postgres records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Easypost and Scaleway Postgres connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Easypost–Scaleway Postgres integration in-house.
Yes — Stacksync ships production-grade connectors for both Easypost and Scaleway Postgres. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Easypost: 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. On Scaleway Postgres: Log-based CDC via PostgreSQL logical replication where the managed instance permits it; otherwise timestamp or query-based polling. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 401 integrations available for Easypost and Scaleway Postgres.