Add 'Acquire an Access Token' page to Lazer how-to guides #842
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.
Description
This PR adds a new standalone "Acquire an Access Token" page to the Lazer how-to guides section. The content was extracted from the existing "Subscribe to Price Updates" guide to create a focused, reusable guide specifically for token acquisition.
Type of Change
Areas Affected
pages/lazer/acquire-access-token.mdx
- Standalone access token guidepages/lazer/_meta.json
- Navigation structurepages/lazer/subscribe-price-updates.mdx
- Cross-reference to new guideChecklist
pre-commit run --all-files
to check for linting errorsKey Review Points
🔍 Please verify:
Screenshots
New standalone page:

Updated navigation and cross-reference:

Related Issues
This addresses a documentation structure improvement by separating the access token acquisition process into its own dedicated guide, making it easier for users to find and reference this critical first step.
Additional Notes
The content was extracted from the existing "Subscribe to Price Updates" guide (specifically the "Acquire an access token" section) to improve discoverability and create a reusable reference. The original guide now links to this new standalone page, maintaining the user flow while improving documentation organization.
Contributor Information