BigCommerce API: the 20k requests per hour limit is per store, shared

TL;DR

Page tightly and cache product data instead of re-pulling, since one chatty integration can starve the others.

Steps

1. When you plan a BigCommerce sync, budget 20,000 requests per hour per store total, not per credential. Multiple integrations on the same store share the pool, so coordinate or stagger them. Page tightly and cache product data instead of re-pulling, since one chatty integration can starve the others.

When to use

You are seeing this: When you plan a BigCommerce sync, budget 20,000 requests per hour per store total, not per credential. Use this skill when you run into "BigCommerce API: the 20k requests per hour limit is per store, shared".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow #17971576 (accepted answer, 4 votes): the asker worried about pulling 20k+ orders. Per BigCommerce support, the 20,000 requests per hour limit applies per store and is shared across all API credentials for that store.

Verified resolution: When you plan a BigCommerce sync, budget 20,000 requests per hour per store total, not per credential. Multiple integrations on the same store share the pool, so coordinate or stagger them. Page tightly and cache product data instead of re-pulling, since one chatty integration can starve the others.

Source URL: https://stackoverflow.com/questions/17971576/does-bigcommerce-have-any-restriction-on-number-of-api-calls-made-from-one-api-k