Fill gaps from assistant conversations: HighLevel app type and frontend API key exposure - #688
Open
mintlify[bot] wants to merge 2 commits into
Open
Fill gaps from assistant conversations: HighLevel app type and frontend API key exposure#688mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Address two recurring assistant conversation themes by clarifying existing pages: users configuring HighLevel with the wrong App Type, and users unsure whether frontend API keys are exposed in production.
Changes
<Warning>under step 4 of app creation stating that HighLevel apps must be Public. Private apps do not support the OAuth redirect URL and client credential flow Ampersand uses, and cannot be connected.<Warning>in the API key authentication section explaining that keys passed toAmpersandProviderare visible in browser network requests and JavaScript, are not time-bound, and are not user-scoped. Directs production readers to JWT authentication.Context
Assistant query buckets in the last week showed:
Both were answered correctly by the assistant, but the source pages did not state these points explicitly.