What we do
Tools
Industries
Department
How we workLet's talk →
Home/BigCommerce/BigCommerce APIs
BigCommerce

The BigCommerce APIs: Which One You Need, How to Authenticate, and the Limits

BigCommerce has more than one API, and they're aimed at different jobs. Back-office syncs use the REST Management API. Headless and custom storefronts use the GraphQL Storefront API. Webhooks tell you when something changed. Here's which is which, how to make a first call, and the rules that decide whether a sync keeps working.

Which BigCommerce API for which job

You want to Use Authenticate with
Sync orders, products, customers or stock with an ERP, 3PL or accounting system REST Management API. Catalog is on v3; orders still sit on v2. A store-level or app-level API account token in the X-Auth-Token header.
Build a headless or custom storefront GraphQL Storefront API, for catalog, cart and checkout. More on headless BigCommerce. A storefront token for browser calls, or a private token for server-to-server calls.
Change a cart from inside a Stencil theme REST Storefront API No BigCommerce token. It runs in the shopper's session on the store's own domain.
React the moment an order or product changes Webhooks, created through /v3/hooks The same API account. Your endpoint must be on port 443.
Work across several stores under one account GraphQL Account API An account-level API account.

Your first REST call

  1. 1

    Create a store-level API account

    Settings Store-level API accounts Create API account

    Give it a name that says what it's for, like "ERP order sync", and grant only the scopes that job needs: orders read-only, products modify, and so on.

    Watch for: scopes can't be changed after the account is created. If you need more later, you make a new account and swap the token.

  2. 2

    Save the access token and note the store hash

    Store the token in a secrets manager, not in the code. The store hash is the short ID in the API path, api.bigcommerce.com/stores/{store_hash}/.

  3. 3

    Call an endpoint

    Send GET https://api.bigcommerce.com/stores/{store_hash}/v3/catalog/products with X-Auth-Token: <token> and Accept: application/json. For orders, the path uses v2.

  4. 4

    Read the rate limit headers on the response

    Every response tells you the window size, the quota and how many calls are left. Build your client to read them from the first call, not after the first 429.

BigCommerce REST rate limits

Limits are counted per 30-second window and depend on the store's plan. The response headers X-Rate-Limit-Requests-Left and X-Rate-Limit-Time-Reset-Ms say where you stand.

Quota per 30 seconds, from BigCommerce's developer docs
Core and Growth plans (about 20,000 an hour) 150 requests
Scale plan (about 60,000 an hour) 450 requests
Performance plans (by plan and resource) Varies
Over the quota (wait for the reset time, then retry) HTTP 429

A 429 with no rate limit headers usually means the store is under heavy load. Wait longer and back off gradually. GraphQL Storefront has its own limits: a complexity score of 10,000 per request, query depth of 16 and one mutation per request.

Why a BigCommerce sync works in testing and fails in production

Treating the webhook as the order

How you'll know: Your handler expects order details and finds only an ID.

Fix: BigCommerce webhook payloads are deliberately light. Take the ID, return 200, then fetch the full order from the API in a background job.

Slow responses to webhooks

How you'll know: The same order arrives several times, or deliveries start backing up.

Fix: Reply 200 straight away and do the work afterwards. Anything other than a fast 200 counts as a failure and is retried.

A deactivated webhook nobody noticed

How you'll know: Orders stop reaching the ERP, and an email about it went to an inbox nobody reads.

Fix: Failed deliveries are retried at growing intervals for up to 48 hours, then the webhook is switched off. Run a scheduled API check for recent orders as a backstop, and alert on gaps.

A bulk catalog load that hits 429 halfway

How you'll know: Some products updated, some didn't, and the log shows a wall of errors.

Fix: Batch requests, pace them against the headers, and resume from the last product that succeeded instead of starting over.

Server calls on a storefront token

How you'll know: A headless back end gets refused by the GraphQL Storefront API.

Fix: Newer storefront tokens don't support server-to-server calls. Use a private token for those.

Securing your webhook endpoint

When you create a webhook you can include a headers object, and BigCommerce sends those headers with every callback. Use it to add a shared secret or basic auth, and reject any request without it. Payloads only carry IDs, and you fetch the details with your own token, so a forged call can't feed you fake order data. It can still make you do work, which is why the check matters.

Custom fields on products and orders are the other thing to plan for. Decide early how each one maps into your ERP or accounting system, because that mapping is what breaks when the catalog changes. See BigCommerce integrations for common targets like NetSuite, and B2B Edition if you sell wholesale, since its API has its own base URL and needs an X-Store-Hash header.

n-frames builds and runs BigCommerce API syncs for stores that would rather not own this: webhooks with a scheduled backstop, calls paced to the plan's quota, and custom fields mapped to the system on the other end. Inventory is a common one to sync first.

Questions people ask

Do I need to be a developer to use the BigCommerce API?

Creating the API account in the store's settings is a few clicks. Building something that calls the API, handles errors and keeps running is development work, or a job for someone like n-frames.

What's the difference between the BigCommerce REST API and the Storefront API?

The REST Management API is for back-office work with a secret token: orders, products, customers and stock. The Storefront APIs, GraphQL and REST, are for building the shopping experience, including headless storefronts. More on headless BigCommerce.

Are there rate limits on the BigCommerce API?

Yes. REST calls are limited per 30-second window by plan, for example 150 on Core and Growth and 450 on Scale, and the response headers show how many calls are left and when the window resets. A call past the limit comes back as a 429.

Can BigCommerce send webhooks when something changes?

Yes. Subscribe to scopes like store/order/created or store/product/updated through the webhooks API, and BigCommerce posts a short payload with the ID to your HTTPS endpoint. Failed deliveries are retried for up to 48 hours before the webhook is deactivated.

Is the BigCommerce API v2 or v3?

Both, side by side. Most newer resources, including the catalog, are on v3. Orders and a few older resources are still on v2. The path in each request says which.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.