Skip to content
E-commerce ⇄ Database

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

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.

  • 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 MarkLogic

Give your engineers Easypost's products, orders, and customers in MarkLogic: 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 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.

Common use cases

  • 01 Feed harmonized entities into search and analytics applications as documents change.
  • 02 Sync curated master data from a MarkLogic data hub into operational CRMs and ERPs.
  • 03 When an order is ready to ship in an OMS, ERP, or database, create an EasyPost Shipment, buy the lowest qualifying Rate, and write the label URL and tracking code back onto the order.
  • 04 Create a Tracker for every outbound shipment and stream tracker.updated webhook events into Postgres or a warehouse so support and ops see live delivery status beside order records.

Common sync patterns

Read the store's data with a query

Records from Easypost, whether products, orders, customers, or inventory, live in MarkLogic 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 MarkLogic, so jobs and triggers can respond the moment an order, price, or stock level changes.

What you can sync between Easypost and MarkLogic

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.

How changes propagate between Easypost and MarkLogic

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

MarkLogic Easypost Interval-based propagation

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.

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.
What ships with Easypost ⇄ MarkLogic

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Easypost ⇄ MarkLogic 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 MarkLogic.

How the Easypost and MarkLogic 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

MarkLogic

Integration surface
REST API (Client API), plus SQL/ODBC access over TDE views and Java/Node client libraries
Authentication
Username/password (digest or basic), with certificate-based options
Change detection
No exposed transaction log; polling on document timestamps/metadata, or server-side triggers that record changes for pickup
Capabilities
read · write
How it works

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

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Easypost ⇄ MarkLogic
    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 MarkLogic
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Easypost and MarkLogic 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 396 integrations available for Easypost and MarkLogic.

Popular · 7 of 396
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.