Source type

BigCommerce Source Configuration

BigCommerce sources receive store, order, cart, product, and customer HTTPS webhooks using Standard Webhooks verification.

BIGCOMMERCEPOST, PUT, PATCH, DELETEClient SecretCommerce
BigCommerce HTTPS webhooks documentationAll source types
BigCommerce sends webhook traffic to a FastHook source, FastHook validates the provider contract, records the request, and routes accepted events through connections to destinations.BigCommerceProviderPOST, PUT, PATCH, DELETESignedFastHookSource URLBIGCOMMERCEProvider credentialsignatureVerify before queue401 on auth failure405 on wrong methodAcceptedRequestverified: trueConnections route the accepted request to destinationsFilters, transformations, retries, replay, and destination signatures stay downstream from source verification.

BigCommerce configuration

Create a BigCommerce source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Client Secret values for provider signature. FastHook uses these settings to validate each BigCommerce delivery before it enters the routing workflow.

Source Type

BIGCOMMERCE

Allowed methods

POST, PUT, PATCH, DELETE

Authentication

Provider signature

Credential fields

Client Secret

BigCommerce source config
{
  "type": "BIGCOMMERCE",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "BIGCOMMERCE",
      "webhook_signing_secret": "provider-secret"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

BigCommerce request contract

FastHook verifies webhook-signature over webhook-id + '.' + webhook-timestamp + '.' + raw body using the configured Standard Webhooks secret.

POSTPUTPATCHDELETE

BigCommerce headers

Preserve webhook-id, webhook-timestamp, webhook-signature when sending BigCommerce test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

webhook-id

Message id used in the Standard Webhooks signed payload.

webhook-timestamp

Unix timestamp used for replay protection and signature input.

webhook-signature

One or more Standard Webhooks signatures.

BigCommerce setup

  1. Create a BigCommerce HTTPS webhook with the generated FastHook Source URL.
  2. Copy the BigCommerce client secret or encoded Standard Webhooks secret into FastHook.
  3. Route by scope such as store/order/created or store/product/updated.

BigCommerce routing hints

  • BigCommerce store events are best separated by scope, for example store/order/created, store/cart/updated, or store/product/inventory/updated.
  • Keep the store hash and producer fields with the event so multi-store receivers can choose the correct tenant and catalog context.

Continue with BigCommerce