Fill gaps from assistant conversations: API key one-time visibility - #313
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
PR author is in the excluded authors list. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Clarify that a Terminal49 API key's full value is only shown once, right after creation, and give readers a concrete recovery path.
Changes
api-docs/getting-started/start-here.mdx: added a warning under "Get an API key" telling readers to copy and store the full token before navigating away, and to create a replacement key if the original was not captured.api-docs/api-reference/introduction.mdx: expanded the Authentication section to spell out the exact header format expectations (noBearer, no quotes, no whitespace), explain what a401 Unauthorized"API key could not be verified" response means, and repeat the one-time-visibility warning.Context
Multiple recent assistant conversations came in from users who could not find the full API key value in the developer portal (the value they saw was masked) and from users hitting
401-style verification errors. The docs did not previously mention that the full key is only revealed at creation time, or how to recover if it was not captured.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.