The expires_in and refresh_token_expires_in values are actually Unix timestamps of the expiration time, multiplied by 60 and then by 1000. This information might not be explicitly mentioned in the documentation and can be confusing.
Your proposal to either update the documentation or change the field names to expires_at and refresh_token_expires_at, using Unix timestamps directly, seems like a practical improvement.
When creating a token (and refreshing), you will receive the following JSON response:
The expires_in and refresh_token_expires_in values are actually Unix timestamps of the expiration time, multiplied by 60 and then by 1000. This information might not be explicitly mentioned in the documentation and can be confusing.
Your proposal to either update the documentation or change the field names to expires_at and refresh_token_expires_at, using Unix timestamps directly, seems like a practical improvement.