BigCommerce subscriber webhook events
BigCommerce sends 3 subscriber events: store/subscriber/created, store/subscriber/updated and store/subscriber/deleted.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
store/subscriber/created
documented from BigCommerce docs (example)
store/subscriber/created New newsletter subscriber added
Identified by scope field in the body
Resource subscriber
{
"scope": "store/subscriber/created",
"store_id": "1000000",
"data": { … },
"hash": "bdb6c9c2d17ca7036538e483db0bdd7debc4beb4",
"created_at": 1561482953,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561482953 |
Full schema: 8 fields.
From BigCommerce docs
-
Content type
application/json
store/subscriber/updated
documented official schema
store/subscriber/updated Newsletter subscriber changes
Identified by scope field in the body
Resource subscriber
{
"scope": "store/subscriber/updated",
"store_id": "1025646",
"data": { … },
"hash": "bdb6c9c2d17ca7036538e483db0bdd7debc4beb4",
"created_at": 1561482953,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561482953 |
Full schema: 8 fields.
From BigCommerce docs
-
Content type
application/json
store/subscriber/deleted
documented official schema
store/subscriber/deleted Newsletter subscriber removed
Identified by scope field in the body
Resource subscriber
{
"scope": "store/subscriber/deleted",
"store_id": "1025646",
"data": { … },
"hash": "bdb6c9c2d17ca7036538e483db0bdd7debc4beb4",
"created_at": 1561482953,
"producer": "stores/{store_hash}"
} Key fields
| Field | Type | Example |
|---|---|---|
created_at | integer | 1561482953 |
Full schema: 8 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.