When you plan bulk pulls against the BigCommerce API, budget against the store, not the key. The 20k requests per hour ceiling is shared by every API key on the store, so adding more keys or parallel workers does not raise it. Spread large order and catalog syncs across the hour window, and if you run multiple integrations on one store, coordinate their call volume against the single shared budget.

Context: Stack Overflow #17971576 (accepted answer, 4 votes): the asker pulled order and product data for stores with 20k+ orders and wanted to know the per-API call limits. BigCommerce support confirmed the 20k requests per hour limit applies to the store as a whole and is shared across all API keys on that store.