Lab - Configure API Credentials and Channel

Preparing for Your Storefront Integration

The BigCommerce APIs are the linchpin of your front-end’s integration with the platform, so the first step for your development journey is to generate the appropriate access credentials to allow your application to access those APIs. We’ll be generating two types of credentials: Store-level v2/v3 API account credentials and a GraphQL Storefront API token.

Prerequisites

• A BigCommerce sandbox store or trial store, or a full production store, with an available slot for a new storefront channel
• Postman or a similar API client

In this lab, you will:

• Practice generating store-level v2/v3 API credentials
• Create a headless storefront channel
• Practice generating a GraphQL storefront token with Postman
• Generate and store the credentials you will use in subsequent labs

Enable Multi-Storefront

If you are using a BigCommerce store for which you’ve already created a Catalyst channel in Introduction to Catalyst, you will need to ensure that Multi-Storefront is enabled in order to create the additional channel in this exercise.

1. In your BigCommerce store control panel, navigate to Channel Manager.
2. Click the “Create channel” button.
3. If you don’t already have the ability to create new storefront slots, an “Enable storefront seats” button will appear in the Storefronts section. Click this button.

You will be presented with a prompt to confirm or update to the various requirements for Multi-Storefront.

4. Confirm or update each item in the requirements list.
5. Exit the channel creation process. (You won’t be creating a storefront channel via the control panel.)

Create a Store-Level API Account

1. In your BigCommerce store control panel, under Settings, navigate to “Store-level API accounts” and create a new “V3/V3 API token” account with the following scopes.

After saving your API account, you will be presented with three values in a modal:

• Client ID
• Client Secret
• Access token

These values will not be retrievable once the displayed modal is closed!

2. Securely store the access token for your API account. Optionally, you may also store the client ID and client secret.

Create a Headless Storefront Channel

While you will use the default storefront of your BigCommerce store for redirected checkout in subsequent labs, we’re going to create a separate, dedicated channel for your headless storefront itself.

1. Create a new Postman environment with the following variables.

2. Create a Postman collection and give it an appropriate name, such as “BC Composable Storefronts Intermediate.”
3. Create a new “Create Headless Channel” HTTP request and save it to your collection. This request requires the following details.

4. In the Headers tab, use the Presets drop-down to Manage Presets, then add a header preset with the following values, saving it with a name like “BC REST.”

5. Select your newly created header preset to populate headers.
6. In the Body tab, select “raw” as the body type and “JSON” from the list of formats. Enter the following body, replacing name with a storefront name of your choice.

{
    "name": "My Headless Storefront",
    "type": "storefront",
    "platform": "next",
    "status": "active",
    "is_visible": true,
    "is_listable_from_ui": true
}

Do not send the request just yet, as we will first add tests and logic to store the ID of the new channel.

7. In the Script tab, enter the following “Post-response” value:

pm.test("Response is not an error", () => {
    pm.response.to.not.be.error;
    pm.response.to.not.have.jsonBody("errors");
});
pm.test("Response is JSON with data", () => {
    pm.response.to.have.jsonBody("data");
});
pm.test("Response includes a channel ID", () => {
    pm.expect(pm.response.json().data?.id).to.be.a("number");
});

These tests will ensure that the channel has been successfully created by examining the response for the channel ID.

8. Add the following after the previous code in the Scripts tab.

pm.environment.unset("storefront_channel_id");
pm.environment.set("storefront_channel_id", pm.response.json().data?.id);

This will store the ID of the new channel permanently in an environment variable alongside your other configuration details.

9. Save the request, make sure you have selected your BigCommerce environment in the environment drop-down, then send the request and observe the results.
10. Send the request and verify that the tests pass in the “Test Results” tab of the response panel.
11. Verify that the storefront_channel_id variable is populated in your environment variables list.

Verify Your Channel Site

1. Create a new HTTP request and save it in your collection with the name “Get Channel Site.”
2. Set the same configuration that was used for the previous request for Authorization and Headers (using your previously created preset).
3. Set the request method as “GET.”
4. Set the following as the URL of the request:

https://api.bigcommerce.com/stores/{{store_hash}}/v3/channels/{{storefront_channel_id}}/site

5. Send the request and observe the response. Verify that your channel contains a “canonical” URL value with the pattern https://store-{hash}-{channel ID}.mybigcommerce.com. This is the URL that will be used for GraphQL Storefront API requests.
6. Observe the checkout URL in the response, which should be set to the URL of your default BigCommerce storefront. This is the configuration you’ll keep for your Redirected Checkout flow in your dev environment.

Your channel does not yet have a “primary” URL, and while working with the channel in a local development environment, you will not have a public domain to set. The main implication of this will be that BigCommerce will not know how to properly generate links to your local headless storefront in your control panel or in Stencil pages like checkout.

In a full build, once you have a public domain and a strategy for checkout domain, you can update these with the following API endpoints:

• Update a Channel Site
• Upsert a Site’s Checkout URL

Create a Private Token (for server-to-server)

Your storefront application’s primary interactions with BigCommerce will use the GraphQL Storefront API. For server-to-server use (including the Next.js app in the next lab), you need a Private Token. Normal/storefront tokens are deprecated for S2S: tokens created after June 30, 2026 do not support S2S; tokens created on or before that date support S2S only until March 31, 2027. Create your Private Token now and store it in private_token.

1. Create a new “Create Private Token” HTTP request and save it to your collection.
2. Set the same configuration that was used for the previous Create a Channel request, including the HTTP method, Authorization, Headers (using your previously created preset), and Body type.
3. Set the request URL to:

https://api.bigcommerce.com/stores/{{store_hash}}/v3/storefront/api-token-private

4. Enter the following body:

{
  "channel_id": {{storefront_channel_id}},
  "expires_at": 2147483647,
  "scopes": [
    "Unauthenticated",
    "Customer",
    "B2B"
  ]
}

5. In the Scripts tab, add the following “post-response” value.

pm.test("Response is not an error", () => {
    pm.response.to.not.be.error;
    pm.response.to.not.have.jsonBody("errors");
});
pm.test("Response is JSON with data", () => {
    pm.response.to.have.jsonBody("data");
});
pm.test("Response includes token", () => {
    pm.expect(pm.response.json().data?.token).to.be.a('string');
});
const token = pm.response.json().data?.token;
if (token) {
    pm.environment.unset("private_token");
    pm.environment.set("private_token", token);
}

6. Send the request and verify that the tests pass in the “Test Results” tab of the response panel.
7. Verify that the private_token variable is populated in your environment variables list. You will use this token (as BIGCOMMERCE_STOREFRONT_TOKEN) in the Next.js app in the next lab.

Assign Catalog Data

Remember that existing catalog data in your store, if it exists, will not automatically be associated with your new channel. You must create a unique category tree for the channel and assign products.

1. Log into your BigCommerce store control panel.
2. In Products > Product Categories, create a category tree for your new channel.

3. Create two or more top-level categories, making sure to assign them to the appropriate channel.
4. If you have existing products in your store that you want to use on your headless channel, visit Products > View and check the checkboxes next to all products you want to assign.
5. Use the bulk actions at the top of the product list to Add to Channels. Select your headless channel and Add.
6. Add your products to categories within your headless channel’s category tree. You can use the Add to Categories bulk action as appropriate, for each group of products you wish to add to a particular category.

If you prefer to create new products for use in your headless channel, subsequent labs will outline the necessary fields you will want to include for the features you’ll be building.

Configure Shipping and Payments

If you want to be able to complete checkout on your Catalyst storefront, you’ll need to make sure you have the appropriate minimal store configuration in place for shipping and payments.

This step is not channel-specific, so if you’ve previously configured shipping and payment options for your store, you won’t need to do any additional setup.

We won’t walk through the details of configuring your store settings, but make sure you have:

• A Shipping Zone that applies to any billing address you will use at checkout
• An enabled Shipping Method on the Shipping Zone
• An enabled test/sandbox Payment Method. (Check the “Enable test credit card payments” option in your Payments Methods settings for the simplest option.)

Resources

• Postman Overview
• Store-Level API Accounts
• Get All Channels
• Update a Channel Site
• Upsert a Site’s Checkout URL
• Shipping Zones
• Shipping Methods