AsyncAPI channel · ShipMonk · ShipMonk Webhooks

receiving/status-change

## Supported Receiving Webhooks All receiving-related webhooks are closely tied to the status of the receiving. Each webhook is triggered when the receiving transitions to a specific `status`, reflecting key milestones in the receiving process. - Receiving awaiting (`status`: `awaiting`) - Receiving in progress (`status`: `in_progress`) - Receiving arrived (`status`: `arrived`) - Receiving receiv

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

Channel address

receiving/status-change

Operations

receive
receiveReceivingStatusChange
Emitted on every change of a receiving `status` (awaiting, in_progress, arrived, received).

Messages

receivingStatusChange
Emitted on every change of a receiving `status` (awaiting, in_progress, arrived, received).
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.