Skip to content
E-commerce ⇄ Database

Easypost to Google Cloud Spanner integration — real-time, two-way sync

Keep Easypost and Google Cloud Spanner 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 Google Cloud Spanner

Give your engineers Easypost's products, orders, and customers in Google Cloud Spanner: 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 Address, Parcel, Rate, Tracker from Easypost into Google Cloud Spanner 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 Google Cloud Spanner, 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 billing or entitlement changes from finance tools into Spanner tables the application reads at runtime.
  • 02 Use change streams to feed near-real-time copies of operational tables into an analytics warehouse.
  • 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

Read the store's data with a query

Records from Easypost, whether products, orders, customers, or inventory, live in Google Cloud Spanner 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.

React to store changes

Updates in Easypost arrive as row changes in Google Cloud Spanner, so jobs and triggers can respond the moment an order, price, or stock level changes.

What you can sync between Easypost and Google Cloud Spanner

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 Google Cloud Spanner 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. Change streams Capture inserts, updates, and deletes for log-style change data capture. Shipment is specific to Easypost and Change streams to Google Cloud Spanner — 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. Views Read-only projections useful for shaping data before it leaves Spanner. Address is specific to Easypost and Views to Google Cloud Spanner — 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. Databases Top-level containers that scope schema and sync configuration. Parcel is specific to Easypost and Databases to Google Cloud Spanner — 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. Tables Relational tables mapped one-to-one to sync targets. Rate is specific to Easypost and Tables to Google Cloud Spanner — 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. Rows The unit of read and write in each sync cycle, keyed by primary key. Tracker is specific to Easypost and Rows to Google Cloud Spanner — 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. Interleaved tables Child rows physically co-located with parents; synced as related records. Batch is specific to Easypost and Interleaved tables to Google Cloud Spanner — each maps to any object or custom field on the other side.

How changes propagate between Easypost and Google Cloud Spanner

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

Google Cloud Spanner Easypost Sub-second propagation

DetectionChanges in Google Cloud Spanner are captured at the source via change data capture — no polling loop against its API. Change streams (log-style CDC), or timestamp-based polling queries.

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.
  • Google Cloud Spanner: Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
What ships with Easypost ⇄ Google Cloud Spanner

Connect Easypost and Google Cloud Spanner for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Easypost ⇄ Google Cloud Spanner 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 Google Cloud Spanner.

How the Easypost and Google Cloud Spanner 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

Google Cloud Spanner

Integration surface
gRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects)
Authentication
Google Cloud IAM (service accounts)
Change detection
Change streams (log-style CDC), or timestamp-based polling queries
Capabilities
read · write · CDC
Rate limits
Throughput is bounded by the instance's provisioned compute capacity rather than a fixed API quota.
How it works

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

    Choose tables

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

Easypost and Google Cloud Spanner 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 385 integrations available for Easypost and Google Cloud Spanner.

Popular · 7 of 385
All Easypost integrations All Google Cloud Spanner 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