I try to extract activity time series data by date range. However, there is a limit on how far back I can go in number of days and this differs from individual to individual. For some subjects I can extract 693 days of data, for other subjects it differs and I can't find the exact limit. Is this specified somewhere?
Answered! Go to the Best Answer.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
I know with some of the activity resources, you can only query a certain amount of data which is approximately 1M bytes. This would explain why you can query X amount of days for one user by not the next. My recommendation is to reduce your interval to 3 - 6 months. This should prevent you from hitting any type of response size restriction.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Hi @KULKver
I will clarify this the documentation. In the meantime, which resource are you querying with the activity time series endpoint? Some of the resource have different restrictions.
Gordon
I'm querying steps, distance, calories, etc., almost everything that can be queried. For all of these activities, I provide a begin and end date. And often the time period between begin and end date is too large causing the error that too many data points are being requested.
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
I know with some of the activity resources, you can only query a certain amount of data which is approximately 1M bytes. This would explain why you can query X amount of days for one user by not the next. My recommendation is to reduce your interval to 3 - 6 months. This should prevent you from hitting any type of response size restriction.