No public API keys
There is no open developer signup or public production credential flow.
PRIVATE DESIGN-PARTNER PROGRAM
Merchant API access is currently available only through a phased design-partner program. Proposed V1 resources and events are evaluated with qualified partners; public self-service access is not live.
DRAFT CONTRACT PRINCIPLES
The parts of the draft that will not be negotiated away. The proposed V1 is built for teams that automate carefully: a safe retry returns the original response instead of a duplicate order, and a resource ID alone is never enough to read data.
Idempotent order creation with stored-response replay
Signed webhooks (HMAC over the raw body) with immutable event IDs
At-least-once delivery your receiver can deduplicate
Per-merchant, per-environment key scoping and isolation
Estimates always distinguished from final packed quotes
PROPOSED V1 SURFACE
Candidate resources may include merchant references, supplier parcels, receiving events, consolidation requests, packed quotes, shipment status and exceptions. Exact fields, event ownership and availability are design topics, not published contracts.
merchant_referenceproposedsupplier_parcelproposedreceiving_eventproposedconsolidation_requestproposedpacked_quoteproposedshipment_eventproposedexceptionproposedNOT CURRENTLY PUBLIC
There is no open developer signup or public production credential flow.
Event ownership, retries and data boundaries must be qualified during design.
No marketplace plugin is represented as installed or generally available.
The proposed scope follows parcels and decisions, not SKU inventory operations.
INTEGRATION QUALIFICATION
We need to understand the systems, technical owner, webhook owner, proposed data flows and sandbox capability before discussing a pilot.