Refreshing the Access Token: To avoid service disruptions, the partner must refresh the access token before it expires. This is done using the refresh token that was provided at the time of authentication.
How It Works: The refresh token can be used to obtain a new access token without requiring the partner to re-authenticate, allowing seamless continued access to the API.
When to Re-authenticate: If the refresh token itself has expired or if the token refresh request fails (due to network issues, server issues, etc.), the partner will be required to re-authenticate. This step is crucial to ensure the integrity and security of the access process.
Why Re-authentication is Needed: Re-authentication serves as a security measure to ensure that unauthorized parties cannot access the system with invalid or expired tokens. It effectively resets the authentication cycle to verify the partnerโs identity.
Stay Updated on Token Status: Partners should always check the validity of their refresh token before initiating API requests to avoid unexpected authentication failures.
Security First: Re-authentication is mandatory in case of refresh token failure to prevent malicious actors from gaining unauthorized access to the API.
Token Lifespan Awareness: Be mindful of the token's expiration timeline to maintain uninterrupted access to the system.
Reminder: Keep track of token expiration times and ensure timely refreshing or re-authentication to maintain a secure and seamless experience with the API.