Hello Fitbit team,
Hoping you can help me! We have integrated the Fitbit API into our website and we are going to have lots of people on the website using the API to find and record their food and exercise throughout the day. However, we saw in the API documentation that we are only allowed 150 requests per hour without a user access token (the “client rate limit”).
Right now, since all the people using our website are using Fitbit (either a scale or tracker), they will have their own user access token and we don’t have an issue. However, moving forward, we will be allowing users who do not have a Fitbit or a Fitbit account and we cannot force them to make one - we fear our application may need more than 150 requests per hour. What are our options to increase the 150 requests limit for the future (pricing options, etc.)? Is there a way to do this?
Thank you!
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
