AsyncAPI channel · ShipBob · ShipBob Webhooks

legacy.order_shipped

Legacy v1.0/v2.0 topic delivered with the legacy header set (`shipbob-subscription-id`, `shipbob-topic`). Fires when a shipment label has been printed. New integrations SHOULD subscribe to `order.shipped` via the current REST surface.

Open source AsyncAPI → All ShipBob channels ShipBob provider profile
Provider: ShipBob AsyncAPI: v2.6.0 Spec: ShipBob Webhooks Operations: 1 Messages: 1

Channel address

legacy.order_shipped

Operations

subscribeLegacyOrderShipped
Receive legacy order_shipped events.

Messages

ShipBobLegacyWebhook
A ShipBob webhook HTTP POST delivery using the legacy v1.0/v2.0 header format.
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.