How do you deauthorising an athlete from the app side?

I’m not a developer myself, but this is the info I have: https://developers.strava.com/docs/authentication/#deauthorization

Hi ​@nairnski,

Thanks for your questions. 

1. Yes, the athlete should see the application no longer appear in the My Apps page.
2. The number of connected athletes within the API Application Settings page is dynamic; deauthorizing athletes will be removed from this count and you’ll have “room” in your capacity for additional athletes.

I just tried the de-authorize endpoint for my test user and got a 200 response.  For the test user, the app was no longer listed in their “My Apps,” but for the API application, it didn’t decrement the connected user count.  Is there a lag?

In my experience the connected athlete count is only periodically updated. I’m not sure exactly what the frequency is but it appears to be at least 24 hours. One thing I haven’t checked is if the athlete count returned in API headers is accurate, that may also be worth checking.

Thanks, that’s great to know!

In this case, I think the number actually was pretty quickly increasing and decreasing, however, there appeared to be some bug where I had a single-player account (for testing), and I authorized an account that wasn’t the single-player (my personal account)!  Not sure how this happened, but I can confirm that I was receiving data for that other account at the rate specified.  Anyway, when I deauthorized the personal account, it didn’t decrement the connected users.  When I deauthorized the test account, the connected users dropped from 1 to 0.