AsyncAPI channel · ShipStation · ShipStation Webhooks

/shipstation/webhook

Single subscriber endpoint that receives every ShipStation webhook event for the registered subscription. ShipStation sends one event per HTTP POST. The `resource_type` field on the JSON body identifies the event class; the `resource_url` field is a fully-qualified HTTPS URL on `ssapi.shipstation.com` that the subscriber should GET (using its ShipStation Basic Auth credentials) to retrieve the res

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

Channel address

/shipstation/webhook

Operations

publish
receiveShipStationWebhook
Receive a ShipStation webhook event

Messages

OrderNotifyEvent
A new order has been imported into ShipStation.
Content-Type: application/json
ItemOrderNotifyEvent
A new order has been imported, scoped to the items on the order.
Content-Type: application/json
ShipNotifyEvent
An order has been shipped.
Content-Type: application/json
ItemShipNotifyEvent
An order has been shipped, scoped to the shipped items.
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.