Fix: Update field key from 'expires' to 'expires_in' in AccessTokenResponse
#231
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.
This update modifies the
AccessTokenResponseclass to correctly parse theexpires_infield from the token response payload.Background
The API response returns the following structure:
{ "access_token": "Atza|IwEBIA***", "refresh_token": "Atzr|IwEBIGk6***", "token_type": "bearer", "expires_in": 3600 }However, the previous implementation attempted to retrieve the token expiration value using the incorrect key
'expires'.Change Summary
self.expires_in = kwargs.get('expires')➡️ to
self.expires_in = kwargs.get('expires_in')This ensures correct parsing of the
expires_infield and avoids potential issues with missing or incorrect token expiration handling.