Authorization

BigCommerce Store Management
Prerequisites
Before creating a BigCommerce Store Management credential in Nexla, you need to create a Store API Credential in your BigCommerce store and obtain your store hash and API key. BigCommerce Store Management API uses API key authentication with the X-Auth-Token header for secure API access.
BigCommerce Store API Credentials Setup
BigCommerce Store Management API requires Store API credentials for authentication. These credentials are used to authenticate requests to the BigCommerce Store Management REST API.
-
Access BigCommerce Control Panel: Sign in to your BigCommerce Control Panel.
-
Navigate to API Settings: Go to Advanced Settings → API Accounts (or Settings → API Accounts depending on your BigCommerce version).
-
Create Store API Credential: Click Create API Account or Create V2/V3 API Token to create a new Store API credential. This will generate:
- API Key: A unique identifier for your API credential
- Store Hash: A unique identifier for your store (found in the API URL or credential details)
-
Configure API Scopes: Ensure your Store API credential has the necessary scopes to access the data you need. The credential needs appropriate permissions for the Store Management API endpoints you plan to use (e.g., read access for products, orders, customers).
-
Copy Credentials: Copy your API Key and Store Hash immediately after creation. Keep these credentials secure, as they provide access to your BigCommerce store data.
BigCommerce Store API credentials provide programmatic access to your BigCommerce store. Keep your API Key and Store Hash secure and do not share them publicly or commit them to version control systems. The API key is sent in the
X-Auth-Tokenheader for all API requests. For detailed information about creating Store API credentials, see the BigCommerce API documentation.
For additional information about BigCommerce Store Management API authentication and credential management, see the BigCommerce API documentation.
Create a BigCommerce Store Management Credential
- To create a new BigCommerce Store Management credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – BigCommerce Store Management

Credential Name & Description
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
BigCommerce Store Management API Configuration
-
Enter your BigCommerce store hash in the Store Hash field. This should be the store hash generated by BigCommerce when you created your Store API Credential. The store hash is a unique identifier for your store and is used to construct the API endpoint URL. You can find your store hash in the API credential details or in the API URL format
https://api.bigcommerce.com/stores/{store_hash}/.... -
Enter your BigCommerce API key in the API Key field. This should be the API key generated by BigCommerce when you created your Store API Credential. The API key is used to authenticate requests to the BigCommerce Store Management API.
The Store Hash and API Key are used to authenticate requests to the BigCommerce Store Management API. The API key is sent in the
X-Auth-Tokenheader for all API requests. Keep your API key secure and do not share it publicly or commit it to version control systems. For detailed information about BigCommerce API authentication, see the BigCommerce API documentation.
Save the Credential
-
Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.
-
The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.