docs(api): better document refresh token behavior - #894
Merged
Conversation
…nd error handling
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
1 participant
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
Clarifies how OAuth refresh tokens behave and documents the error response returned when a token exchange fails.
Addresses the documentation follow-up from #888.
Changes
400OAuth error response.refresh_tokenfields.Risk
Low. These changes affect contract documentation and the generated OpenAPI error schema without changing authentication behavior.
Notes
The documentation guide has already been updated with a "Refreshing an Access Token" section: https://docs.trakt.tv/docs/authentication-oauth