08-11-2015 17:40
08-11-2015 17:40
Answered! Go to the Best Answer.
01-07-2016 12:56
01-07-2016 12:56
Look at the Fitbit-Rate-Limit-* headers in the HTTP response. These are documented here.
08-12-2015 11:04
08-12-2015 11:04
Please see the rate limit documentation at https://dev.fitbit.com/docs/basics/#rate-limits
There is no difference in the rate limit between OAuth 1.0a and OAuth 2.0.
You can always see your remaining rate limit by looking at the rate limit headers in the API response.
01-07-2016 00:59 - edited 01-07-2016 02:56
01-07-2016 00:59 - edited 01-07-2016 02:56
Thank you for your reply.
How could I check the client rate limit or the number of API requests which have been sent?
My application aims to make GET request for activities' information like step, walking, running each time synchronizing fitbit account.
How could I check the limit of steps (or walk or run) could be sent before reaching the client rate limit?
Our oauthorization setting information is as following
.siteUrl = "https://api.fitbit.com/oauth"
.profile_json = "https://api.fitbit.com/1/user/-/profile.json"
.devices_json = "https://api.fitbit.com/1/user/-/devices.json"
.activities = "https://api.fitbit.com/1/user/-/activities/"
.limit.days = 14
If you have time could you check the above information
(oauth information like consumerKey and consumerSecret can be sent by private message)
Thank you and I am looking foward to hearing your reply.
01-07-2016 12:56
01-07-2016 12:56
Look at the Fitbit-Rate-Limit-* headers in the HTTP response. These are documented here.
01-07-2016 14:39
01-07-2016 14:39
The limit is imposed per user account per application. It's an implicit relationship, 1:1. So you could have many accounts and the same user could sign up on each account, and each relationship between account and user will each have their own separate limits.
As Jeremiah said:
Rate Limits
The Fitbit API has two separate rate limits on the number of calls an app can make. Both are hourly limits that reset at the start of the hour.
01-07-2016 23:48 - edited 01-08-2016 00:59
01-07-2016 23:48 - edited 01-08-2016 00:59
@JeremiahFitbit wrote:Look at the Fitbit-Rate-Limit-* headers in the HTTP response. These are documented here.
Thank you for you reply.
runscope should be used for debug HTTP response header?
https://dev.fitbit.com/docs/help/#debugging-with-runscope
Actually I would to capture the number of raw data (steps) so if there is any recommendation, please notice me.
01-08-2016 12:02
01-08-2016 12:02
Headers are part of the response. You should search for how your HTTP library exposes them to your application.
You can certainly use Runscope to inspect requests, but you don't need to use Runscope to figure out the rate limit in the response.
See the activity intraday time series for minute-by-minute step data.
01-12-2016 00:14
01-12-2016 00:14
Thank you for your support.
This helped me much.
I got my header response data that shows 'Fitbit-Rate-Limit*'