The Subscription API is used for notifying 3rd party applications when a user's Fitbit data changes. On July 24, 2020, a new collection type was released to notify your subscriber when a user has revoked access to your application.
Fitbit users have the ability to stop sharing their data with an application by revoking access (or consent) to that application through their Fitbit account settings. When the user revokes access to the application, the user's access tokens and refresh token become invalid, and the user's subscriptions are automatically deleted.
Fitbit can now send a notification when a user revokes access to the application via the associated subscriber. To receive these notifications, the application needs to subscribe to the collection type userRevokedAccess. The userRevokedAccess collection type is supported for the Add Subscription, Delete Subscription, and Get Subscription List endpoints. When referencing all collections with the subscription endpoints, userRevokedAccess is included.
The notification will contain the collection name, the date the user revoked access, the Fitbit user ID, the owner type, and the subscription ID.
Example notification:
{
"collectionType":"userRevokedAccess",
"date":"2020-06",
"ownerId":"user",
"subscriptionId":"1234"
}
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Best Answer