From bigcommerce-commerce
Implements BigCommerce webhooks: manage store events like orders/products/customers, handle/verify payloads, add retry logic for real-time integrations.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin bigcommerce-commerceThis skill is limited to using the following tools:
**Fetch live docs**:
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Fetch live docs:
https://developer.bigcommerce.com/docs/integrations/webhooks for webhooks guidesite:developer.bigcommerce.com webhooks events reference for event topicsbigcommerce webhook payload format for payload structureWhen events occur in a BigCommerce store, HTTP POST requests are sent to your endpoint:
POST /v3/hooksPOST /v3/hooks
{
"scope": "store/order/created",
"destination": "https://your-app.com/webhooks/orders",
"is_active": true,
"headers": {
"X-Custom-Header": "my-verification-value"
}
}
GET /v3/hooks — returns all registered webhooks.
PUT /v3/hooks/{id} — update destination, scope, or active status.
DELETE /v3/hooks/{id} — remove a webhook.
| Topic | When |
|---|---|
store/order/created | New order placed |
store/order/updated | Order modified |
store/order/archived | Order archived |
store/order/statusUpdated | Order status changed |
store/order/message/created | Order message added |
store/order/refund/created | Refund issued |
| Topic | When |
|---|---|
store/product/created | New product created |
store/product/updated | Product modified |
store/product/deleted | Product deleted |
store/product/inventory/updated | Stock level changed |
store/product/inventory/order/updated | Inventory changed due to order |
| Topic | When |
|---|---|
store/customer/created | New customer registered |
store/customer/updated | Customer profile modified |
store/customer/deleted | Customer deleted |
store/customer/address/created | Address added |
store/customer/address/updated | Address modified |
| Topic | When |
|---|---|
store/cart/created | New cart created |
store/cart/updated | Cart modified |
store/cart/deleted | Cart deleted |
store/cart/converted | Cart converted to order |
store/cart/abandoned | Cart abandoned |
store/cart/lineItem/* | Line item changes |
| Topic | When |
|---|---|
store/shipment/created | Shipment created |
store/shipment/updated | Shipment modified |
store/subscriber/created | Newsletter subscriber added |
store/category/created | Category created |
store/category/updated | Category modified |
store/sku/created | SKU created |
store/sku/updated | SKU modified |
store/app/uninstalled | App uninstalled |
{
"scope": "store/order/created",
"store_id": "1234567",
"data": {
"type": "order",
"id": 5678
},
"hash": "abc123def456...",
"created_at": 1706140800,
"producer": "stores/{store_hash}"
}
scope — the event topicstore_id — the store's numeric IDdata.type — resource typedata.id — resource ID (use to fetch full details via API)hash — unique event hash for deduplicationcreated_at — Unix timestampWebhook payloads contain only the resource ID, not the full resource. You must make a follow-up REST API call to fetch the complete data:
// Webhook says: order 5678 was created
// Fetch full order: GET /v2/orders/5678
is_active set to false when deactivatedhash for idempotency)Include custom headers in webhook registration for basic verification:
{
"headers": {
"X-Webhook-Secret": "my-secret-value"
}
}
Verify the header value in your handler to confirm the request is from BigCommerce.
hash field for idempotency (deduplication)Fetch the BigCommerce webhooks documentation for the complete list of event topics, payload formats, and retry behavior before implementing.