Two-way sync
Changes in Easypost or MarkLogic instantly reflect in both systems. No stale data, no manual imports.
Keep Easypost and MarkLogic 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 MarkLogic 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 MarkLogic, 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.
Records from Easypost, whether products, orders, customers, or inventory, live in MarkLogic as ordinary tables or collections, joinable with the rest of your data.
Scripts and services read and write the synced tables; Stacksync handles the Easypost API, rate limits, and retries.
Updates in Easypost arrive as row changes in MarkLogic, so jobs and triggers can respond the moment an order, price, or stock level changes.
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 | MarkLogic objects | How this pairing syncs | |
|---|---|---|---|
| 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. | TDE Views Relational projections of documents that let syncs read document data as SQL rows. | Rate is specific to Easypost and TDE Views to MarkLogic — 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. | Document Metadata & Properties Permissions, quality, and property fragments carried with each document. | Tracker is specific to Easypost and Document Metadata & Properties to MarkLogic — 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. | Databases & Forests Storage units that define the scope and placement of synced content. | Batch is specific to Easypost and Databases & Forests to MarkLogic — 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. | Users & Roles Security principals that govern what an integration credential can read or write. | CarrierAccount is specific to Easypost and Users & Roles to MarkLogic — each maps to any object or custom field on the other side. | |
| 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. | Documents JSON and XML documents, the primary records read from and written to the database. | Webhook is specific to Easypost and Documents to MarkLogic — each maps to any object or custom field on the other side. | |
| 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. | Collections Named groupings used to scope which documents a sync reads or updates. | Shipment is specific to Easypost and Collections to MarkLogic — 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 MarkLogic as a row-level write, with types converted between the two schemas.
DetectionStacksync polls MarkLogic for changes on an incremental schedule, reading only records changed since the previous pass. No exposed transaction log.
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–MarkLogic connection.
Changes in Easypost or MarkLogic instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Easypost or MarkLogic 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 MarkLogic record.
Track your Easypost ⇄ MarkLogic sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Easypost and MarkLogic.
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 MarkLogic 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 MarkLogic 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 MarkLogic: authenticate both systems, choose the objects to sync (such as Easypost's Rate and Tracker), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Easypost and MarkLogic. 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 MarkLogic: No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the MarkLogic side: TDE Views, Document Metadata & Properties, Databases & Forests, Users & Roles, plus custom fields where MarkLogic exposes them. On the Easypost side: Tracker, Batch, CarrierAccount, Webhook. 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 Easypost and MarkLogic: Read the store's data with a query; Internal tools and automations without API code; React to store changes. Records from Easypost, whether products, orders, customers, or inventory, live in MarkLogic as ordinary tables or collections, joinable with the rest of your data.
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 396 integrations available for Easypost and MarkLogic.