AsyncAPI channel · ShipMonk · ShipMonk Webhooks

order/status-change

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`

Open source AsyncAPI → All ShipMonk channels ShipMonk provider profile
Provider: ShipMonk AsyncAPI: v3.0.0 Spec: ShipMonk Webhooks Operations: 1 Messages: 1

Channel address

order/status-change

Operations

receive
receiveOrderStatusChange
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.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.