Skip to content
Back to Site

BigCommerce API Connection

Create a store-level BigCommerce V2/V3 API token and prepare the Store URL, API Path, Client ID, and Access Token required by Next-Cart.

Use the store owner account to create the store-level API account. BigCommerce permits only the store owner to create these credentials.

  1. Sign in as the store owner. Open Settings and select Store-level API accounts near the bottom of the page. BigCommerce API Account

  2. Click Create API account. Select V2/V3 API token for Token type, enter a name, and copy the API path. BigCommerce API Path

  3. Set the OAuth permissions below. Use Read-only when BigCommerce is the Source Store and Modify when it is the Target Store.

    OAuth scopeData or requirement
    ContentRequired.
    CustomersCustomer data.
    Information & SettingsRequired.
    MarketingRequired.
    OrdersOrder data.
    ProductsProduct data.
    Channel SettingsRequired.
    Channel ListingsRequired.
    Store LocationsRequired when migrating Products.
    Store InventoryRequired when migrating Products.
    BigCommerce API Scopes
  4. Click Save. BigCommerce downloads a .txt credentials file and displays the credentials in a pop-up. BigCommerce API Credentials

  5. Record the API path, Client ID, and Access Token for the API account. Client Secret is not required for the Next-Cart connection.

Next-Cart fieldValue to enter
Store URLThe BigCommerce store URL.
API PathThe API path from this store-level API account.
Client IDThe generated Client ID.
Access TokenThe generated Access Token.

Use Test Platform Connections for optional access verification. A successful test shows Connected.

CheckPass condition
Store identityThe Store URL identifies the intended BigCommerce store or site, and the connection values used below belong to that same environment.
Credentials and valuesAPI Path, Client ID, Access Token are the values obtained for this same intended BigCommerce store, account, or authorization setup.
Permissions or accessThe store-level API account uses the required OAuth access for its migration role: Read-only for Source and Modify for Target.

A Connected result confirms that Next-Cart can access BigCommerce with the supplied connection values. It does not confirm migration configuration, mappings, or final migrated data; validate those separately during the Configuration step and post-migration review.

If the platform remains Not connected, recheck the API Path, Client ID, and Access Token from the same store-level API account and confirm the role-appropriate OAuth permissions, then use the shared recovery checks.