Skip to content
Database ⇄ E-commerce

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

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

Give your engineers Easypost's products, orders, and customers in DuckDB: 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 Parcel, Rate, Tracker, Batch from Easypost into DuckDB 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 DuckDB, 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 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
  • 02 Push aggregates computed in DuckDB out to a CRM or business tools so analysis results reach operational systems.
  • 03 Sync CarrierAccount configuration and negotiated rates so shipping options stay consistent across the storefront, ERP, and 3PL systems.
  • 04 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.

Common sync patterns

Controlled write-back

Choose exactly which tables and fields may flow from DuckDB 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 DuckDB 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 DuckDB and Easypost

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.

DuckDB objects Easypost objects How this pairing syncs
Tables Columnar tables created via SQL; the destination for materialized sync data. 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 is specific to DuckDB and Address to Easypost — each maps to any object or custom field on the other side.
Views SQL views used to shape or filter data for downstream consumers. Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Views is specific to DuckDB and Parcel to Easypost — each maps to any object or custom field on the other side.
External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. 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. External files (Parquet/CSV/JSON) is specific to DuckDB and Rate to Easypost — each maps to any object or custom field on the other side.
Attached databases Additional database files or external systems attached into one session for cross-source queries. 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. Attached databases is specific to DuckDB and Tracker to Easypost — each maps to any object or custom field on the other side.
Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. 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. Database files is specific to DuckDB and Batch to Easypost — each maps to any object or custom field on the other side.
Schemas Namespaces within a database used to organize tables in sync outputs. CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. Schemas is specific to DuckDB and CarrierAccount to Easypost — each maps to any object or custom field on the other side.

How changes propagate between DuckDB and Easypost

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.

DuckDB Easypost Interval-based propagation

DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.

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

Easypost DuckDB 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 applied to DuckDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
  • 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.
What ships with DuckDB ⇄ Easypost

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the DuckDB and Easypost connectors work

DuckDB

Integration surface
In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
Authentication
None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
Change detection
Polling or full re-reads; no change feed or transaction log API
Capabilities
read · write
Rate limits
No API rate limits; throughput is bounded by local compute and I/O

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
How it works

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

    Choose tables

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

DuckDB and Easypost 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 406 integrations available for DuckDB and Easypost.

Popular · 7 of 406
All DuckDB integrations All Easypost 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