BigCommerce order webhook events
11 store-wide order scopes. Most integrations start with store/order/created, then fetch the order from the REST API, because the body holds only its ID.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
store/order/created
documented from BigCommerce docs (example)
store/order/created Order placed, including failed and unprocessed payments
Identified by scope field in the body
Resource order
{
"scope": "store/order/created",
"store_id": "1000000",
"data": { … },
"hash": "dd70c0976e06b67aaf671e73f49dcb79230ebf9d",
"created_at": 1561479335,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479335 |
Full schema: 8 fields.
From BigCommerce docs
-
Content type
application/json
store/order/updated
documented official schema
store/order/updated Any change to an existing order
Identified by scope field in the body
Resource order
{
"scope": "store/order/updated",
"store_id": "1025646",
"data": { … },
"hash": "dd70c0976e06b67aaf671e73f49dcb79230ebf9d",
"created_at": 1561479335,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479335 |
Full schema: 8 fields.
From BigCommerce docs
-
Content type
application/json
store/order/archived
documented official schema
store/order/archived Order moved to the archive
Identified by scope field in the body
Resource order
{
"scope": "store/order/archived",
"store_id": "1025646",
"data": { … },
"hash": "dd70c0976e06b67aaf671e73f49dcb79230ebf9d",
"created_at": 1561479335,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479335 |
Full schema: 8 fields.
From BigCommerce docs
-
Content type
application/json
store/order/statusUpdated
documented from BigCommerce docs (example)
store/order/statusUpdated Order moves to a different status
Identified by scope field in the body
Resource order
{
"scope": "store/order/statusUpdated",
"store_id": "1000000",
"data": { … },
"hash": "7ee67cd1cf2ca60bc1aa9e5fe957d2de373be4ca",
"created_at": 1561479335,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479335 |
Full schema: 11 fields.
From BigCommerce docs
-
Content type
application/json
store/order/message/created
documented from BigCommerce docs (example)
store/order/message/created Customer or control panel message added to an order
Identified by scope field in the body
Resource order
{
"scope": "store/order/message/created",
"store_id": "1000000",
"data": { … },
"hash": "cb07cdbdda8b1965e812693d5988154807eeed02",
"created_at": 1561479923,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479923 |
Full schema: 10 fields.
From BigCommerce docs
-
Content type
application/json
store/order/refund/created
documented from BigCommerce docs (example)
store/order/refund/created Refund submitted against an order
Identified by scope field in the body
Resource order
{
"scope": "store/order/refund/created",
"store_id": "1000000",
"data": { … },
"hash": "cb07cdbdda8b1965e812693d5988154807eeed02",
"created_at": 1561479923,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479923 |
Full schema: 10 fields.
From BigCommerce docs
-
Content type
application/json
store/order/transaction/created
documented from BigCommerce docs (example)
store/order/transaction/created Transaction record added to an order
Identified by scope field in the body
Resource order
{
"scope": "store/order/transaction/created",
"store_id": "1000000",
"data": { … },
"hash": "dd70c0976e06b67aaf671e73f49dcb79230ebf9d",
"created_at": 1561479335,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479335 |
Full schema: 17 fields.
From BigCommerce docs
-
Content type
application/json
store/order/transaction/updated
documented official schema
store/order/transaction/updated Order transaction record changes
Identified by scope field in the body
Resource order
{
"scope": "store/order/transaction/updated",
"store_id": "1025646",
"data": { … },
"hash": "dd70c0976e06b67aaf671e73f49dcb79230ebf9d",
"created_at": 1561479335,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561479335 |
Full schema: 17 fields.
From BigCommerce docs
-
Content type
application/json
store/order/metafield/created
documented from BigCommerce docs (example)
store/order/metafield/created Metafield added to an order
Identified by scope field in the body
Resource order
{
"scope": "store/order/metafield/created",
"store_id": "1000000",
"data": { … },
"hash": "8fd18449531d7e531587782eb200950cbad8cffe",
"created_at": 1683315012,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1683315012 |
Full schema: 8 fields.
From BigCommerce docs
-
Content type
application/json
store/order/metafield/updated
documented official schema
store/order/metafield/updated Order metafield changes
Identified by scope field in the body
Resource order
{
"scope": "store/order/metafield/updated",
"store_id": "1001197568",
"data": { … },
"hash": "8fd18449531d7e531587782eb200950cbad8cffe",
"created_at": 1683315012,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1683315012 |
Full schema: 9 fields.
From BigCommerce docs
-
Content type
application/json
store/order/metafield/deleted
documented official schema
store/order/metafield/deleted Metafield removed from an order
Identified by scope field in the body
Resource order
{
"scope": "store/order/metafield/deleted",
"store_id": "1001197568",
"data": { … },
"hash": "8fd18449531d7e531587782eb200950cbad8cffe",
"created_at": 1683315012,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1683315012 |
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.