Skip to content

B2B-3725 - BC token as an alternative to B2B #1104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
bc-victor wants to merge 1 commit into
base: main
Choose a base branch
from
Open

B2B-3725 - BC token as an alternative to B2B #1104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/storefront/catalyst/development/b2b.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,7 @@ To create a B2B storefront on the Catalyst platform, you will need the following
- Git and a GitHub account.
- Node.js and PNPM.
- A Vercel account. Using your GitHub account to sign up is recommended for ease.
- A V3 BC API token.
- A V3 B2B API token. You can retrieve this from the B2B control panel under the "API Accounts" tab by clicking "Create API account." Ensure it is a V3 API token.
- A BigCommerce store-level API account token used for REST API actions. This integration requires `modify` scope on "B2B Edition". In order to set up our headless storefront domain properly for B2B transactional emails we'll also need a token with `modify` scope for "Sites & Routes".

### 1. Using Catalyst CLI

Expand All @@ -48,6 +47,7 @@ Environment variables to add:
- BIGCOMMERCE_STORE_HASH
- BIGCOMMERCE_STOREFRONT_TOKEN: Use your store API key to get a storefront token. Refer to the BigCommerce developer documentation for [creating a token](https://developer.bigcommerce.com/docs/rest-authentication/tokens#create-a-token).
- BIGCOMMERCE_CHANNEL_ID
- BIGCOMMERCE_ACCESS_TOKEN: A store-level API account token used for REST API actions. This integration requires `modify` scope on B2B Edition for this token.
- ENABLE_ADMIN_ROUTE: Default to `true`.
- AUTH_SECRET: Generate it using `openssl rand -hex 32`.
- TURBO_REMOTE_CACHE_SIGNATURE_KEY: Generate using openssl rand -hex 32.
Expand All @@ -57,7 +57,6 @@ Also add the B2B related environment variables:

- B2B_API_HOST: https://api-b2b.bigcommerce.com.
- This is the domain of the B2B API. NOTE: Make sure this value does not have a trailing slash.
- B2B_API_TOKEN: The V3 B2B API token obtained during the preparation step.

Once all environment variables are set, we can proceed with deployment.

Expand Down