ShipStation Webhooks
Version 1.0.0
AsyncAPI description of the ShipStation V1 outbound webhook surface. ShipStation delivers event notifications by issuing HTTP POST requests with a JSON body to a `target_url` that the customer registers through the `POST /webhooks/subscribe` endpoint (or via the ShipStation UI under Account Settings > Integrations > Integration Partners). Every documented webhook event uses the same envelope payload shape (the `Webhook` model): a `resource_url` that the subscriber must fetch with ShipStation API Basic Authentication credentials to retrieve the triggering resource, and a `resource_type` string that names the event. Per the ShipStation API reference, the four event types in scope here are: - ORDER_NOTIFY — fires when any new order is imported, regardless of store. - ITEM_ORDER_NOTIFY — fires when a new order is imported, with the resource URL scoped to the order items. - SHIP_NOTIFY — fires when an order is shipped. - ITEM_SHIP_NOTIFY — fires when an order is shipped, with the resource URL scoped to the shipped items. Source documentation (ShipStation V1 docs, retrieved from web.archive.org snapshots of www.shipstation.com/docs/api/): - Subscribe to Webhook: /docs/api/webhooks/subscribe/ - List Webhooks: /docs/api/webhooks/list/ - Unsubscribe to Webhook: /docs/api/webhooks/unsubscribe/ - Webhook model: /docs/api/models/webhook/ Security: The HTTP POST that ShipStation sends to `target_url` does not, per the public V1 docs, include a published signing header. The documented authentication path is on the *callback* the subscriber issues back to ShipStation to dereference `resource_url`: the subscriber authenticates to `ssapi.shipstation.com` with HTTP Basic credentials (API key and secret). Subscribers commonly defend the inbound `target_url` with HTTPS plus a hard-to-guess path or embedded Basic credentials.
Channels
Messages
Servers
{targetUrl}