With the Personal API, you can create personal access tokens for the Tredict API, allowing applications to access your own Tredict data. Be it a self-developed Zwift FIT file uploader or a script to automatically transfer Stryd data from the Stryd PowerCentre to Tredict.

Who is the Personal API intended for?

The Personal API is aimed at individual Tredict users and enables users to generate their own access tokens for the Tredict OAuth2 API.

If you have developed an application that should allow other users to access Tredict, then register your application for the OAuth2 API here.: Tredict API - OAuth2 documentation - Apply

How is personal user authorisation managed?

Under ‘Settings -> Personal API’, you can generate personal access tokens, which you then transmit as bearer tokens to the endpoints of the normal Tredict API using an authorisation header.

Automatic token deactivation during inactivity

Your personal tokens are only active if you visit the Tredict web interface at least once every two weeks! After two weeks of user inactivity, the tokens are deactivated for security reasons, but are automatically reactivated the next time you visit. 

Endpoints

You can find a detailed description of the Tredict API endpoints in the Tredict OAuth2 documentation.:
Tredict API - OAuth2 Dokumentation