07-12-2016 06:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-12-2016 06:15
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello!
Our company is using the Fitbit-API with the deprecated OAuth 1.0 standard. We are planning to migrate the accounts from our connected users via calls against the OAuth 2.0 token endpoint, like it is described here:https://dev.fitbit.com/docs/oauth2/#upgrading-to-oauth-2-0.
We will send the requests from our servers and wanted to know if there is a rate-limit for requests against this endpoint. If yes, how many request are we allowed to send per hour?
Approximately 20,000 User-Accounts will be affected by the migration.
Kind Regards
THK
Answered! Go to the Best Answer.

- Labels:
-
OAuth 1.0a
-
OAuth 2.0
Accepted Solutions
07-12-2016 17:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



07-12-2016 17:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
@thk: The upgrade token flow is not rate limited.
07-12-2016 17:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



07-12-2016 17:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
@thk: The upgrade token flow is not rate limited.
07-13-2016 10:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-13-2016 10:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thank you!

