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 Get response slowness

‎04-11-2019 10:37

‎04-11-2019 10:37

Hi Fitbit Team, 

 

Starting today at 10:30AM we are seeing the get response call on the Fitbit is taking more time than usual, average response time is 200ms normally and we could see that it is spiking to 1000ms today from 10:30 AM. 

Can you please check and confirm if there are any latency issues on your end. 

 

 

Best Answer
Labels:
0 Votes
2 REPLIES 2

‎04-11-2019 10:38

‎04-11-2019 10:38

https://api.fitbit.com:443/1/user/-/activities/date/2019-04-11.json this is  the sample get response call that we make to get the data and we are seeing slowness in the call 

Best Answer
0 Votes

‎04-12-2019 14:55

In response to DSGTeam

‎04-12-2019 14:55

Hi @DSGTeam 

 

I am not seeing a performance issue with that endpoint today.  Are you still experience a delay?   

 

Also, is there a reason for including the port number in the API call.  That should not be required.

 

Gordon

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes