DEVDOCS-6508 - Write guide for the Company account registration workflow in B2B Edition's GrapQL APIs #1187
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…low in B2B Edition's GrapQL APIs Created a new guide for Company Account Registration in the GraphQL Storefront API, detailing workflows for guest and existing customers, related queries, and considerations for new Company accounts.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
CNanninga
suggested changes
Dec 23, 2025
|
|
||
| Guest users do not have an existing customer account with login credentials. As a result, the requests involved in the [guest registration workflow](#registration-for-guest-users) can be performed anonymously without a token in the Authorization header. | ||
|
|
||
| The [registration workflow for existing customers](#registration-for-existing-storefront-customers) passes a storefront authToken to the Authorization header. This is a Bearer token generated via the `login` mutation following customer login. While it is included in the header of all B2B Edition GraphQL queries and mutations in the flow, it is only required for the `customer` query, which is a proxy request to the [BigCommerce GraphQL Storefront API](https://developer.bigcommerce.com/docs/storefront/graphql). This request uses the following endpoint: `https://api-b2b.bigcommerce.com/api/v3/proxy/bc-storefront/graphql` |
Contributor
There was a problem hiding this comment.
The phrasing "it is only required for the customer query" made it sound to me like you meant that's the only query in all of the B2B GraphQL API that requires it. (There are, of course, many queries and mutations in the B2B GraphQL that require an auth token.) I think this actually meant it's the only query in this flow that requires it, but some re-wording might avoid confusion.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created a new guide for Company Account Registration in the GraphQL Storefront API, detailing workflows for guest and existing customers, related queries, and considerations for new Company accounts.
DEVDOCS-6508
What changed?
Release notes draft
Anything else?
ping