As an order progresses from initial import to full fulfillment, it transitions through multiple statuses. ShipMonk can notify external systems of these status changes via webhooks.
## Supported Order Webhooks
Currently ShipMonk supports these order-related webhooks.
- Order being back-ordered (`processing_status`: `back-order`)
- Order is unable to submit (`processing_status`: `unable_to_submit`
Emitted on every change of an order `processing_status` (back-order, on_hold, submitted, pick_in_progress, pack_in_progress, packed, awaiting_pick_up, en_route, delivered, undeliverable, shipped_untra
Messages
orderStatusChange
Emitted on every change of an order `processing_status` (back-order, on_hold, submitted, pick_in_progress, pack_in_progress, packed, awaiting_pick_up, en_route, delivered, undeliverable, shipped_untra
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.