Skip to content
Data warehouse ⇄ E-commerce

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

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

Make Databricks the analytics and enrichment layer behind Easypost: orders, products, and customers stay current in both directions.

Databricks is the analytical store where the business joins, models, and reports on its data; Easypost runs the storefront, catalog, and transactions that generate most of it. The overlap is every record that has to be counted and enriched on one side and acted on the other — and when the bridge is a nightly export, the warehouse reports on yesterday while the store operates without the segments and metrics the warehouse just computed.

Stacksync syncs Delta Tables, Views, Materialized Views, Volumes in Databricks with Shipment, Address, Parcel, Rate in Easypost field by field, in real time, and in both directions. Transactional records land in the warehouse as they change, computed attributes and cleaned catalog data flow back to the store, and you decide which system owns which fields so Stacksync resolves conflicts by rules you set.

Common use cases

  • 01 Land CRM and ERP records in Delta tables continuously so lakehouse models work from current operational data.
  • 02 Use Change Data Feed to propagate only changed rows to downstream apps instead of full-table scans.
  • 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

One product catalog

Where both systems hold product or catalog data, cleaned and enriched attributes stay aligned so the store and the warehouse describe the same items.

Inventory and order status reconciled

Stock levels and order or fulfillment status move between Databricks and Easypost so counts and states agree across reporting and operations.

One customer master

Where both systems keep customer records, corrections in either propagate to the other so analytics and the storefront share one identity.

What you can sync between Databricks 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.

Databricks objects Easypost objects How this pairing syncs
Materialized Views Precomputed results read on a schedule for reverse-ETL style syncs. Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. Materialized Views is specific to Databricks and Parcel to Easypost — each maps to any object or custom field on the other side.
Volumes Unity Catalog file storage used for staging bulk loads. 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. Volumes is specific to Databricks and Rate to Easypost — each maps to any object or custom field on the other side.
SQL Warehouses The compute endpoint a sync connects to for query execution. 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. SQL Warehouses is specific to Databricks and Tracker to Easypost — each maps to any object or custom field on the other side.
Change Data Feed Row-level change records on Delta tables that drive incremental reads. 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. Change Data Feed is specific to Databricks and Batch to Easypost — each maps to any object or custom field on the other side.
Catalogs Top level of the Unity Catalog namespace, scoping which schemas a sync can address. CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. Catalogs is specific to Databricks and CarrierAccount to Easypost — each maps to any object or custom field on the other side.
Schemas Group tables and views; syncs typically target a dedicated schema per source system. 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. Schemas is specific to Databricks and Webhook to Easypost — each maps to any object or custom field on the other side.

How changes propagate between Databricks 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.

Databricks Easypost Sub-second propagation

DetectionChanges in Databricks are captured at the source via change data capture — no polling loop against its API. Delta Lake Change Data Feed for row-level changes.

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

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

Rate-limit considerations

  • Databricks: Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits.
  • 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 Databricks ⇄ Easypost

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Databricks and Easypost connectors work

Databricks

Integration surface
SQL over JDBC/ODBC via SQL warehouses, plus a REST API including statement execution
Authentication
Personal access tokens or OAuth machine-to-machine credentials for service principals
Change detection
Delta Lake Change Data Feed for row-level changes; otherwise incremental polling on watermark columns
Capabilities
read · write · CDC
Rate limits
Throughput depends on the SQL warehouse size; API calls are subject to workspace rate limits

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 Databricks 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 Databricks 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
    Databricks connected
    Easypost connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Databricks 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 508 integrations available for Databricks and Easypost.

Popular · 8 of 508
All Databricks 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