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: 

Fitbit api calls slower?

ANSWERED

‎05-06-2016 05:29

‎05-06-2016 05:29

Hi,

 

I'm making use of the Fitbit API Oauth 2.0 (which we migrated a few weeks ago) to retrive activity data for some 5k users. Usually it used to take less than an hour to do it, and suddenly today while retriveing it was much more than 2 hours. Nothing has been changed from my side of the code. Is this delay coming from the Fitbit systems? Could an official from Fitbit confirm this please.

 

Regards

Best Answer
Labels:
0 Votes
1 BEST ANSWER

Accepted Solutions

‎05-06-2016 14:04

‎05-06-2016 14:04

Response times in the last 24 hours have been consistent to the previous 24 hours.

View best answer in original post

Best Answer
0 Votes
1 REPLY 1

‎05-06-2016 14:04

‎05-06-2016 14:04

Response times in the last 24 hours have been consistent to the previous 24 hours.

Best Answer
0 Votes