Because
1. your end-user has re-authenticated, invalidating the previous access token or
2. there is more than one access token for the same credentials_id in your database.
Your access_token has a credentials_key attached to it that TrueLayer uses to decrypt the token and provide you with data access. Only the most recent credentials_key is able to decrypt an access_token for a credentials_id.
Still having problems?
- Check if you are storing only the most recent access token in your database.
- Check if your development team are not all using the same
clientId and bank account. You could be invalidating each other's tokens.
If you need more information...
Have a look at our comprehensive list of the authentication error descriptions in our API documentation.
