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: 

Data Synchronization Timing for Heart Rate Intraday Data via Fitbit Web API

4 hours ago

4 hours ago

We are developing an application using the Fitbit Web API, and we have the following question:

How long does it typically take for data after the lastSyncTime (obtained via the Device API) to be fully synchronized on the Fitbit servers?

 

We currently retrieve Heart Rate Intraday data via the Web API approximately 3 hours after obtaining the lastSyncTime. However, we have noticed that additional data sometimes becomes available when checking after a longer period. Could you please advise on how we can verify that the data has been completely synchronized on the server?

We understand that for Activity and Body data, the Subscription feature allows the client to receive data as soon as it is synchronized on the server. However, since Heart Rate data does not support Subscriptions, we would appreciate your guidance on the recommended method to confirm its full synchronization.

Thank you for your assistance.

Best Answer
Labels:
0 Votes
0 REPLIES 0