Authentication Token Expiry
Author:
Fluent Commerce
Changed on:
3 Feb 2025
Overview
Token authentication is mandatory for all Fluent integrations.
Key points
- An authentication token is required for every request.
- You can reuse the same token until it expires.
- When a token is close to expiry, a new one can be requested using the refresh token from the authentication response.
When using Fluent APIs, an authentication token is required for every request. You can reuse the same token until it expires.
Every token has a limited lifetime and can be invalidated for a number of reasons. It will expire periodically.
Integrations built against the APIs will need to manage re-authentication in the event that the token has expired.
Care should, however be taken not to enter an infinite loop for re-authentication in the case of an error.
When an authentication token is close to expiry, a new one can be requested using the refresh token from the authentication response without needing to send the username and password. Refresh tokens are single-use and have a separate expiry time to authentication tokens. See the Authentication API page for more details.