BigCommerce
Org-level connection
BigCommerce is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
Enter your BigCommerce store URL in the Store URL field above
Go to BigCommerce admin → Settings → API → API Accounts
Click "Create API Account" → "Create V2/V3 API Token"
Set a name and select the OAuth scopes you need
Copy the Access Token, Client ID, and Store Hash
Paste them below
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for BigCommerce. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
store_v2_products | Read products | Read only |
store_v2_products_read_only | Write products | Read / Write |
store_v2_orders | Read/write orders | Read / Write |
store_v2_customers | Read/write customers | Read / Write |
store_v2_information_read_only | Read store info | Read only |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
The key expires or stops working
Some API keys have expiration policies. Generate a new key in BigCommerce and update it in On Belay → Integrations → BigCommerce → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →