help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Is there any throttling in the OAuth 2.0 upgrade custom method?

‎11-11-2015 14:51

‎11-11-2015 14:51

Assume I have thousand of users, could I exchange the old token for the new one for everybody in a short window? Any limitation/rule I should pay attention to?

 

Thanks,

Best Answer
Labels:
0 Votes
1 REPLY 1

‎11-11-2015 15:53

‎11-11-2015 15:53

Be reasonable. We'll contact you if there's a problem. There's no rate limit applied to that endpoint. It's fine if you have thousands of users to upgrade, but probably best to not open tens of thousands of HTTPS connections at once.

Best Answer
0 Votes