Thanks for your response, I’ll update my app accordingly then
1 Like
It is as app4g says. I am planning to support multiple access tokens per app soon. That was an oversight on my part.
Coming back to this, is multi access token already supported?
Thanks!
I just implemented that. There can be many access tokens for an athlete linked to an app, once for each time they authorise it. The most recent scopes apply to all access tokens.
3 Likes
Thanks! One more question, is there also a scope for managing my athletes? The use case it’s that coaches will be connecting to intervals.
EDIT: Found it in Swagger, there is a ATHLETES scope, but still doesn’t seem to work.
EDIT2: It seems accessing /athletes seems to work with my own API key but not through the bearer token where I get 403.
Currently oauth tokens grant access to the authorising athlete’s data but not to people they follow or coach. This is by design so someone who follows you can’t auth a 3rd party app which then gains access to your data. I think you need to get each athlete to auth your app and then use the correct token depending on the athlete.
Will this work?
The only (specific) issue to us, it’s that we work with coaches and use there data. Unfortunatly our whole data platform is built around the idea of 1 connection → multiple athletes. This was following the same logic as TrainingPeaks basically, where the coached athletes are also available through the API.