Two-way sync
Changes in Azure Synapse Analytics or Easypost instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Azure Synapse Analytics 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 Materialized views, SQL pools, Tables (dedicated SQL pool), External tables in Azure Synapse Analytics with Parcel, Rate, Tracker, Batch 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.
Where both systems hold product or catalog data, cleaned and enriched attributes stay aligned so the store and the warehouse describe the same items.
Stock levels and order or fulfillment status move between Azure Synapse Analytics and Easypost so counts and states agree across reporting and operations.
Where both systems keep customer records, corrections in either propagate to the other so analytics and the storefront share one identity.
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.
| Azure Synapse Analytics objects | Easypost objects | How this pairing syncs | |
|---|---|---|---|
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | 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. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Shipment to Easypost — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in 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. | External tables is specific to Azure Synapse Analytics and Address to Easypost — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | 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 Azure Synapse Analytics and Parcel to Easypost — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that separate staging, integration, and presentation layers. | 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. | Schemas is specific to Azure Synapse Analytics and Rate to Easypost — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | 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. | Materialized views is specific to Azure Synapse Analytics and Tracker to Easypost — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | 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. | SQL pools is specific to Azure Synapse Analytics and Batch to Easypost — 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.
DetectionStacksync polls Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
DeliveryEach detected change is written to Easypost through its API, with automatic retries and rate-limit backoff.
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 Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Easypost connection.
Changes in Azure Synapse Analytics or Easypost instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics or Easypost data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Azure Synapse Analytics or Easypost record.
Track your Azure Synapse Analytics ⇄ Easypost sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics and Easypost.
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 Azure Synapse Analytics 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.
Pick the Azure Synapse Analytics 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.
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 Azure Synapse Analytics and Easypost: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's Tables (dedicated SQL pool) and External tables), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Azure Synapse Analytics side: Materialized views, SQL pools, Tables (dedicated SQL pool), External tables, plus custom fields where Azure Synapse Analytics exposes them. On the Easypost side: Parcel, Rate, Tracker, Batch. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Azure Synapse Analytics and Easypost: One product catalog; Inventory and order status reconciled; One customer master. Where both systems hold product or catalog data, cleaned and enriched attributes stay aligned so the store and the warehouse describe the same items.
Azure Synapse Analytics: SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint. Authentication: SQL authentication or Microsoft Entra ID. Easypost: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Azure Synapse Analytics: Dedicated SQL pool tables are distributed across compute nodes using hash, round-robin, or replicated strategies, and the choice affects load and query performance for synced tables. 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 Azure Synapse Analytics and Easypost without custom code.
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 499 integrations available for Azure Synapse Analytics and Easypost.