BigCommerce shipment webhook events
BigCommerce sends 3 shipment events: store/shipment/created, store/shipment/updated and store/shipment/deleted.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
store/shipment/created
documented from BigCommerce docs (example)
store/shipment/created New shipment added to an order
Identified by scope field in the body
Resource shipment
{
"scope": "store/shipment/created",
"store_id": "1000000",
"data": { … },
"hash": "8b98021cb0faa7e3a58a0e4182d3696a4bdd24ab",
"created_at": 1561482857,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561482857 |
Full schema: 9 fields.
From BigCommerce docs
-
Content type
application/json
store/shipment/updated
documented official schema
store/shipment/updated Existing shipment changes
Identified by scope field in the body
Resource shipment
{
"scope": "store/shipment/updated",
"store_id": "1025646",
"data": { … },
"hash": "8b98021cb0faa7e3a58a0e4182d3696a4bdd24ab",
"created_at": 1561482857,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561482857 |
Full schema: 9 fields.
From BigCommerce docs
-
Content type
application/json
store/shipment/deleted
documented official schema
store/shipment/deleted Shipment removed from an order
Identified by scope field in the body
Resource shipment
{
"scope": "store/shipment/deleted",
"store_id": "1025646",
"data": { … },
"hash": "8b98021cb0faa7e3a58a0e4182d3696a4bdd24ab",
"created_at": 1561482857,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561482857 |
Full schema: 9 fields.
From BigCommerce docs
-
Content type
application/json
Route BigCommerce events by type.
Event Gateway receives every BigCommerce delivery and filters and routes it by event type, so each service gets only the events it handles.