+1How can my app deauthorize stale users when my app capacity has been reached. Can the expired token still be refreshed so we can then send a “deauthorize” request for it? I need to free up some connections as we have reached our maximum capacity.
Please advise.
Thanks,
Elvin
+26Hi
+1Hi
Can access tokens be refreshed even if our api application capacity (max 9,999) is already reached?
+26As long as the user didn’t revoke the access and you still have the refresh token it can be refreshed. Whether the access token you have stored on your side are expired or not has no influence on Strava’s count of users for your app.
+1As long as the user didn’t revoke the access and you still have the refresh token it can be refreshed. Whether the access token you have stored on your side are expired or not has no influence on Strava’s count of users for your app.
Thank you. But if a user gets “deauthorized”, does the user get removed/deducted from the current count of users/athletes connected?
+26Yes, it does.
+1Is there a way for my to see who are currently connected to my API application? The dashboard only shows the number, for example below:
+1Yes, it does.
Today I connected an athlete who had successfully connected before and the “Number of athletes currently connected” did not increase. Then I deauthorized the same user immediately, and the “Number of athletes currently connected” also did not change.
Can you explain how this number is calculated or updated?
Thanks.
+26It can take some time like a day or two after deauthorizing an athlete until the count decreases. This was implemeted to prevent artifically using more users than granted by repeatingly deauthorizing one athlete and authorizing another in a short timeframe.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.