How to connect to BigCommerce

This guide covers connectivity troubleshooting for the BigCommerce connection.

Troubleshooting: not returning all or any data

If your BigCommerce connection returns fewer records than expected, or a call fails and then succeeds on retry, the usual causes are on the API-usage side — not a firewall or edge block:

• Rate limiting. BigCommerce's API enforces rate limits. Under bursty load individual calls can be throttled and fail transiently; retrying a little later typically succeeds.
• Pagination / page size. BigCommerce caps the number of records returned per request, so a single call will not return an entire catalog or order history. Page through the results (follow the pagination cursor / limit) to retrieve the full set.

Note: Unlike self-hosted stores such as WooCommerce or Magento, BigCommerce is a hosted (SaaS) API — Apideck calls BigCommerce's own API endpoints, so there is no customer-controlled firewall, WAF, or Cloudflare layer in the request path. Allowlisting Apideck's egress IPs is generally not relevant for BigCommerce; focus on rate limits and pagination instead.