Need for a Bulk Unsubscription Process for Users with Invalid/Expired Tokens

[HediDKT]

Hello Fitbit Team,

Following up on the unresolved issue of unsubscribing users with invalid tokens, as discussed in this thread: Unsubscribe from notifications with expired Access Token

We are facing the same problem with our Decathlon application (Client ID: 22DPJK). We receive over a million weekly webhook notifications for users who are inactive on our platform and for whom our tokens have expired.

Because our credentials for these users are invalid, we cannot use the API's revoke or unsubscribe endpoints to stop the notifications.

We formally request a process to bulk unsubscribe these users. We can provide a complete list of the Fitbit User IDs that need to be removed. (new cases are not happening again in our side we avoid expired cases now)

A manual unsubscription handled by your support team would be a viable solution for us. This would greatly reduce unnecessary load on both Fitbit's and our systems.

Thank you for your guidance on how to proceed.

Best regards,

[Gondwana]

(Moved to correct forum section.)