06-05-2014 21:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-05-2014 21:23
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
You can make 150 API requests per hour for each user that has authorized your application to access their data. The counter resets at the top of the hour. Because the rate limit is a per user limit, the total number of users does not affect your application's overall ability to use the API.
More information about the rate limit (headers, client-only request limit, response code) can be found in the Fitbit API rate limit documentation.

- Labels:
-
OAuth 1.0a
06-11-2014 15:56
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-11-2014 15:56
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Got data? Get answers at zenobase.com.

06-11-2014 15:58 - edited 06-11-2014 15:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
06-11-2014 15:58 - edited 06-11-2014 15:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
It depends on if you are using client only credentials or client+viewer credentials.
(If you only send oauth consumer key, then its client only. If you send both oauth consumer key and token, its client+viewer).
The client and client+viewer are separate rate limits. Rate limits are per app and per user (if client+viewer).

06-11-2014 15:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-11-2014 15:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@ejain wrote:
Is the rate limit per user, or per user and app? I just got a 429 when trying to access a user's data for the first time in weeks.
There is both a client rate limit and a client+viewer rate limit (requests signed with your client credentials and user access token). See the documentation for full details.

06-11-2014 16:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-11-2014 16:09
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Got data? Get answers at zenobase.com.

06-11-2014 16:17 - edited 06-11-2014 16:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
06-11-2014 16:17 - edited 06-11-2014 16:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
The rate limit is not shared by different apps. It is certainly possible for you to be able to make requests for one user of your app and get 429 (rate limit exceeded) for another user of your app.
If you private message me your application consumer key, I can take a look for you.
06-11-2014 17:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-11-2014 17:26
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Got data? Get answers at zenobase.com.

06-17-2014 06:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-17-2014 06:20
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Dan,
I am facing the same issue of rate access limit. If you can share your private mail-id then I can explain the use case properly.
Regards,
Kshama

06-17-2014 08:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

SunsetRunner
06-17-2014 08:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
You can private message me here by clicking on my name to the left of this post and then the "send this user a private message" link on the following page.

06-24-2018 02:20 - edited 06-24-2018 05:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-24-2018 02:20 - edited 06-24-2018 05:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi Dan,
I can not send you private message as you tell.
Now I meet same above problem - limit 150 API requests per hour for each user.
Please help me to solve this problem
Thanks

