Add exchangeOtpForCustomerToken mutation #510
Merged
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
jhadobe
approved these changes
Nov 13, 2025
github-project-automation
bot
moved this from 📋 Needs Review
to 👍 Approved
in Commerce - Pull Requests
github-project-automation
bot
moved this from 👍 Approved
to 🏁 Done
in Commerce - Pull Requests
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.
Reverts #508
This pull request adds documentation and navigation support for the new
exchangeOtpForCustomerTokenGraphQL mutation, which allows customers to authenticate using a one-time password (OTP). It also updates related navigation, mutation listings, and usage documentation to include this new mutation and corrects the path for an existing mutation.