Trakt changes the API token lifetime, is this an issue?

[djraw]

Hi there,
as the title states I received following email about token expiration. Does this need to be addressed in the app?

Starting on March 4, 2025, an OAuth access_token will expire in 24 hours, instead of 3 months. Since you've created a Trakt API app, we wanted to let you know directly.

Why are we reducing the expiration?

3 months is a long time and is a potential security risk if the access_token gets intercepted. We're instead going with a much lower 24 hours and relying on apps to automatically use the refresh_token more often to obtain a new access_token.

Do I need to update my app?

Probably not, since you should already be handling expired an access_token and refreshing it automatically. If you're hard coding a refresh interval, we suggest making that check dynamic and based on the expires_in value instead. If you aren't doing this, check out the Trakt API docs.

What about existing access tokens?

They should continue to work up until their expiration date. At that time, your app needs to refresh it and get a new access_token, then use the expires_in value so your app can dynamically handle when to refresh.

How can I contact you?

If you have any questions, please continue the discussion in the GitHub API project.

Happy coding,

• Trakt Engineering Team

[cecobask]

Hi @djraw, this doesn’t apply to the app and changes won’t be required. No need to worry about it 🙂