What causes a Fitbit DEAUTH event?

Fitbit allows only one active authorisation per user, so connecting the same Fitbit account through a second app revokes the first connection and fires a…

Fitbit allows only one active authorisation per user, so connecting the same Fitbit account through a second app revokes the first connection and fires a DEAUTH on the first app.

More generally, deauth events fire when:

• The deauthenticate endpoint is called.

• The user revokes access in the provider's own settings.

• The token is invalidated by a re-authorisation elsewhere.