05-03-2016 14:04
05-03-2016 14:04
Is anything going on with the API today?
Best Answer05-03-2016 14:06
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.
05-03-2016 14:06
We're not aware of anything.
What was the exact request and the response? Are you able to reproduce it?
Best Answer05-03-2016 14:08
05-03-2016 14:08
I cannot reproduce because this hit my rate limit. The exact call was GET /activities/date/{date}.json with the current date inserted.
Best Answer05-03-2016 15:07
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.
05-03-2016 15:07
That's not a valid endpoint. Did you intend GET /1/user/[user-id]/activities/date/[date].json ?
Best Answer05-03-2016 15:16
05-03-2016 15:16
My apologies. Yes, the full endpoint that I used is GET /1/user/[user-id]/activities/date/[date].json - I apologize it was cut off in my last message. It appears that Fitbit does not have paging set up. This is something that I did not take into account. Do you why this is?
Best Answer05-03-2016 16:18
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.
05-03-2016 16:18
That endpoint is the daily summary, which returns a bunch of data about that specific day. If you want specific data (such as steps, heart rate, etc), you should request those resources individually instead.
If someone logged 69 manual logs on that day, the daily summary endpoint is behaving correctly.
Best Answer