BigCommerce store webhook events

BigCommerce sends 7 store events, including store/hook/deliveryException, store/app/uninstalled and store/information/updated. 6 have sample payloads.

Every event here can also reach agents as an MCP event through Hookdeck: MCP events →

store/hook/deliveryException

documented from BigCommerce docs (example)

A webhook's destination is failing, retrying or blocked

Identified by scope field in the body Resource store

bigcommerce-store-hook-deliveryexception.json
{
  "scope": "store/hook/deliveryException",
  "store_id": "1025646",
  "data": { … },
  "hash": "e0c298b8097a6a2f39d17e593a9b360f5b2fef7d",
  "created_at": 1561482670,
  "producer": "stores/{store_hash}"
}

Key fields

Field Type Example
created_at integer 1561482670

Full schema: 10 fields.

From BigCommerce docs

  • Content type application/json

Send example to Inspect → View as JSON

store/app/uninstalled

documented No payload yet

Store cancelled and the app uninstalled

Identified by scope field in the body Resource store

No payload yet.

Help fill this in → View as JSON

store/information/updated

documented from BigCommerce docs (example)

Store settings change

Identified by scope field in the body Resource store

bigcommerce-store-information-updated.json
{
  "scope": "store/information/updated",
  "store_id": "1000000",
  "data": { … },
  "hash": "c553845e0a5e28dc8b0ea494458692a25586a294",
  "created_at": 1535489273,
  "producer": "stores/{store_hash}"
}

Key fields

Field Type Example
created_at integer 1535489273

Full schema: 7 fields.

From BigCommerce docs

  • Content type application/json

Send example to Inspect → View as JSON

store/redirects/updated

documented from BigCommerce docs (example)

Redirects created or changed, one event per request

Identified by scope field in the body Resource store

bigcommerce-store-redirects-updated.json
{
  "scope": "store/redirects/updated",
  "store_id": "1025646",
  "data": [ … ],
  "hash": "c553845e0a5e28dc8b0ea494458692a25586a294",
  "created_at": 1535489273,
  "producer": "stores/{store_hash}"
}

Key fields

Field Type Example
created_at integer 1535489273

Full schema: 12 fields.

From BigCommerce docs

  • Content type application/json

Send example to Inspect → View as JSON

store/store/metafield/created

documented from BigCommerce docs (example)

Metafield added at store level

Identified by scope field in the body Resource store

bigcommerce-store-store-metafield-created.json
{
  "scope": "store/store/metafield/created",
  "store_id": "1025646",
  "data": { … },
  "hash": "c553845e0a5e28dc8b0ea494458692a25586a294",
  "created_at": 1535489273,
  "producer": "stores/{store_hash}"
}

Key fields

Field Type Example
created_at integer 1535489273

Full schema: 9 fields.

From BigCommerce docs

  • Content type application/json

Send example to Inspect → View as JSON

store/store/metafield/updated

documented official schema

Store-level metafield changes

Identified by scope field in the body Resource store

bigcommerce-store-store-metafield-updated.json
{
  "scope": "store/store/metafield/updated",
  "store_id": "1025646",
  "data": { … },
  "hash": "c553845e0a5e28dc8b0ea494458692a25586a294",
  "created_at": 1535489273,
  "producer": "stores/{store_hash}"
}

Key fields

Field Type Example
created_at integer 1535489273

Full schema: 9 fields.

From BigCommerce docs

  • Content type application/json

Send example to Inspect → View as JSON

store/store/metafield/deleted

documented official schema

Store-level metafield removed

Identified by scope field in the body Resource store

bigcommerce-store-store-metafield-deleted.json
{
  "scope": "store/store/metafield/deleted",
  "store_id": "1025646",
  "data": { … },
  "hash": "c553845e0a5e28dc8b0ea494458692a25586a294",
  "created_at": 1535489273,
  "producer": "stores/{store_hash}"
}

Key fields

Field Type Example
created_at integer 1535489273

Full schema: 9 fields.

From BigCommerce docs

  • Content type application/json

Send example to Inspect → View as 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.

Not affiliated with BigCommerce. Facts are compiled from public sources and linked inline.