Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My BigCommerce integration keeps failing or has stopped

Short answer

BigCommerce documents three common causes. All apps on a store share one API quota, and a 429 answer means it was used up. Webhooks are switched off after a failed delivery run and stay off until re-enabled. And a request only works if the API account has the right scope.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Orders or stock stopped flowing to my other system.
  • It works for a while and then fails, usually when the shop is busy.
  • Errors mention 429 or too many requests.
  • New orders do not trigger anything any more, but nobody changed anything.
  • A connection that worked yesterday now says it has no permission.

Why does this happen?

  1. All apps share one quota

    BigCommerce says each API request uses one unit of quota and that all apps on a store share it. Once it is used up, later requests are rejected until it refreshes. OAuth apps are limited by a quota that refreshes every 30 seconds.

  2. A 429 is the store saying slow down

    A 429 Too Many Requests answer means the limit was hit. BigCommerce recommends reading the X-Rate-Limit-Time-Reset-Ms header and waiting that long, spreading requests over time with queues or batching, and caching results that are asked for often.

  3. Webhooks switch themselves off

    BigCommerce says a webhook destination must answer with HTTP 200, and failed deliveries are retried at growing intervals for 48 hours. After the final retry the webhook is deactivated and an email goes to the address registered for the app. It stays off until its is_active flag is set back to true.

  4. Webhooks carry little data

    BigCommerce says a webhook payload is light, for an order status change it contains only the order id, so the receiving system has to call the API for the full details. A slow or failing call at that step looks like a lost order.

  5. The account needs the right scope

    BigCommerce says a request only succeeds if the API account has the required scope, and advises the minimum scope that the integration needs. Changing an app's scopes refreshes its token and the store owner must reauthorise the app. A deleted store-level API account cannot be recovered.

What can I do about it today?

  1. Write down when it stoppedNote the date, the first order or product that did not sync, and what changed around then, such as a new app or a sale.
  2. Check your email for webhook warningsBigCommerce emails the address registered for the app when a webhook is deactivated. Search for it, including the spam folder.
  3. Do not delete API accounts or appsA deleted store-level account cannot be recovered, and the connected systems would stop for good. Leave the settings as they are until someone has looked.
  4. List every app and system connected to the storeThey all draw on the same quota, so the list shows who might be using it up.
  5. Ask the integration's owner for the exact errorA status code and a time are enough: 429, 401, 403 or a timeout each point in a different direction.

When should I bring someone in?

  • Orders are not reaching your warehouse, accounting or shipping system.
  • The problem keeps returning during busy periods.
  • Nobody knows who built the integration or holds its credentials.

How do I handle it?

  1. Reproduce with logsI look at the status codes and headers of failed calls and match them against BigCommerce's documented behaviour.
  2. Re-enable and verify webhooksI check is_active on each webhook, fix the reason for failure first, then switch it back on and watch a real order arrive.
  3. Make calls gentleRequests are queued, batched and cached, and the code waits for the reset time that BigCommerce reports after a 429.
  4. Answer fast, process laterThe receiving endpoint replies at once, which BigCommerce recommends, and does the slow work in the background.
  5. Close the gapsA catch-up job compares recent orders on both sides and replays any that were missed while the integration was down.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How long does BigCommerce keep retrying a failed webhook?

Its documentation says retries run at growing intervals and stop after a total of 48 hours from the first attempt, after which the webhook is deactivated.

Is a 429 a bug in my store?

No. It is the store's documented way of saying the request limit was reached. BigCommerce also says a 429 without the rate limit headers can point to high load on the store, and the request can be retried later.

Will missed orders be sent again automatically?

Not after the webhook has been deactivated. Orders from that period have to be found and replayed, which is why I compare both sides after fixing the cause.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.