We have the following scenario coming up a couple of times by now:
What particular case from today: For a certain user we received a lot of notification about new date. We did not receive this notification only once every couple hours, but rather every couple of seconds. In the course of ~50minutes we received over 300 notifications, all for the same user, all for the same day (2020/03/11).
Naturally, since we're handling each and every single notifications we sooner or later run into the 15 minutes rate limit by Fitbit, causing all subsequent requests to be discarded.
What is the recommended way of handling these issues?
Can Fitbit prevent the multiple notifications since it doesn't make sense to send them over and over again?
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