Documentation Ecommerce and inventory BigCommerce

Ecommerce integration

BigCommerce

BigCommerce integration overview
  • CategoryEcommerce
  • AuthAPI token

Overview

BigCommerce (listed as "Big eCommerce" in the integrations grid) connects on /integrations in the dashboard. Click the Big eCommerce card and the 'Connect to Big eCommerce' modal takes three fields: API Token, Client ID and Client Secret, and Store Hash. The AI uses the token as the X-Auth-Token header on every REST call to BigCommerce, scoped per store by the Store Hash in the URL path. On save the credentials are stored on your tenant; product sync is a separate switch on the integration page, and turning it on registers product webhooks on your store so later catalog changes arrive live. Every inbound webhook is verified with HMAC-SHA256 against a per-store signing secret before anything is acted on.

What MessageMind can do with it

  • Import the entire BigCommerce product catalog (physical and digital) in paginated passes at the API's maximum page size of 250 per page.
  • Keep the catalog current by receiving store/product/created, store/product/updated and store/product/deleted webhooks when product sync is on.
  • Register and remove product webhooks per store directly through BigCommerce's /v2/hooks endpoint when sync is toggled.
  • Verify every inbound webhook payload with HMAC-SHA256 using the per-store signing secret before acting on it.
  • Resolve the storefront's domain and name from the Store Information endpoint so the AI can label products with the shop they came from.

Requirements

  • A BigCommerce store the merchant can create an API Account on.
  • A BigCommerce API Account token with scopes covering the product and webhook surfaces MessageMind reads from and manages.
  • The store's Store Hash (the identifier BigCommerce uses in its per-store REST URLs).

How to connect

  1. In the BigCommerce control panel, open Settings, API Accounts and create a new Store API Account. Grant it access to the resources it will manage (products, webhooks).
  2. Copy the API Token, the Client ID and Client Secret, and your Store Hash before leaving the page; BigCommerce only shows the token once.
  3. In the MessageMind dashboard, open /integrations and click the Big eCommerce card. The 'Connect to Big eCommerce' modal opens.
  4. Fill in the three fields labelled 'API Token', 'Client ID and Client Secret', and 'Store Hash', then save.
  5. Once stored, toggle product sync on from the Big eCommerce integration page to register the product webhooks on your store.

Authentication and permissions

Mechanism
BigCommerce API Account token sent as the X-Auth-Token header on every REST call, scoped per store by Store Hash in the URL path. Inbound webhooks are verified with HMAC-SHA256 using a per-store signing secret.
Credentials
API Token, Client ID (with Client Secret) and Store Hash stored on your tenant, plus the per-store webhook signing secret.

Available data and actions

Reads

  • Products across the BigCommerce v3 catalog, paginated at the API maximum of 250 per page.
  • Store information (secure URL and name) from the v2 Store endpoint.
  • Existing webhooks registered on the store (/v2/hooks), used to decide what needs to be created, kept or removed.

Writes

  • Webhook subscriptions on the store itself, created and deleted through POST and DELETE /v2/hooks when product sync is toggled.

AI agent use cases

  • A shopper asks about a product on a channel the AI is listening on; the AI quotes details from the synced BigCommerce catalog.
  • A merchant updates a product in BigCommerce; the webhook arrives, MessageMind verifies its HMAC, and the catalog refreshes without a manual re-import.
  • A merchant removes a product; the delete webhook retires the row from the AI's view.

Configuration

  • Product sync is a per-store toggle. When sync is off, product webhooks are dropped on arrival with no work done.
  • The order webhook scope (store/order/created) exists in the integration but is not yet wired for order automations; the current allowlist carries product scopes only.

Example workflows

Keep the product catalog in step

  1. Merchant turns product sync on from the Big eCommerce integration page.
  2. MessageMind registers the three product webhooks on the store (created, updated, deleted) through /v2/hooks.
  3. On every subsequent product change in BigCommerce, the webhook fires.
  4. MessageMind verifies the HMAC signature, confirms the credentials and product sync are still active, then updates its own view of the catalog.

Limitations

  • The order webhook scope is reserved for a future order flow; the current integration allowlist does not accept order webhooks.
  • Webhooks for a shop whose credentials have been removed, or whose product sync was switched off, are silently dropped (responded to with 200) rather than acted on.

Troubleshooting

Webhooks do not reach MessageMind after turning sync on.

Confirm the registered webhook address matches the MessageMind public webhook URL and that the API Account token still has access to the webhook resource on the store.

Reads fail with 401 or 403.

The API Account token was revoked or lost its scopes. Issue a new token in BigCommerce, Settings, API Accounts and update it in MessageMind.

Disconnect and reconnect

  • On /integrations in the dashboard, open the Big eCommerce card and choose Disconnect. The stored API Token, Client ID, Client Secret and Store Hash are removed from your tenant.
  • In BigCommerce, delete the API Account under Settings, API Accounts to revoke it store-side.
  • To reconnect, create a fresh API Account in BigCommerce and paste its credentials into the same card.