AsyncAPI channel · ShipMonk · ShipMonk Webhooks

return/status-change

## Supported Return Webhooks All return-related webhooks are closely tied to the status of the return. Each webhook is triggered by a specific status transition, marking important stages in the return process. - Return created (`status`: `status_created`) - Return in progress (`status`: `in_progress`) - Return en route (`status`: `en_route`) - Return returned (`status`: `returned`) ## Payload St

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

Channel address

return/status-change

Operations

receive
receiveReturnStatusChange
Emitted on every change of a return `status` (status_created, in_progress, en_route, returned).

Messages

returnStatusChange
Emitted on every change of a return `status` (status_created, in_progress, en_route, returned).
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.