Note unique API token names per project#241
Open
mintlify[bot] wants to merge 1 commit into
Open
Conversation
Generated-By: mintlify-agent
Contributor
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
Upstream change: API token creation now enforces unique token names per project. If a user tries to create a token with a name that is already in use by an active token in the same project, the request returns a 409 Conflict and the dashboard surfaces an inline error prompting them to pick a different name.
Docs change
Updated
cloud/migrate-to-standard.mdx(the only place in the docs that walks users through generating an API token) to mention the new uniqueness requirement so users aren't surprised by the validation error when generating tokens forPORTER_TOKENor other CI use cases.No other docs pages reference API token creation flow.