Status: Draft 0.1 · 2026-10-06 · Editor: Daniel Kobina (Eben Labs) This is an open specification for a universal, multi-carrier shipping API. Any party can implement it: Every mode shares the same core: rates, shipments, pickups, tracking, webhooks, and one object model. Platforms consume it once and reach every implementer. See Modes. The API borrows Stripe’s conventions on purpose: prefixed IDs, Idempotency-Key, cursor pagination, expand[], metadata, dated versions, test and live keys, and signed webhook events.

Explore

The Industry Map shows every party, platform module and canonical object in three views (orbit, journey lanes and matrix), with shipment simulations. It links back into these pages.

Two audiences

Normative language

MUST, MUST NOT, SHOULD, SHOULD NOT and MAY are used as defined in RFC 2119 and RFC 8174.