05-03-2016 14:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-03-2016 14:04
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Is anything going on with the API today?

- Labels:
-
Subscriptions API
05-03-2016 14:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-03-2016 14:06
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
We're not aware of anything.
What was the exact request and the response? Are you able to reproduce it?

05-03-2016 14:08
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-03-2016 14:08
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I cannot reproduce because this hit my rate limit. The exact call was GET /activities/date/{date}.json with the current date inserted.

05-03-2016 15:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-03-2016 15:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
That's not a valid endpoint. Did you intend GET /1/user/[user-id]/activities/date/[date].json ?

05-03-2016 15:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-03-2016 15:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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?

05-03-2016 16:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-03-2016 16:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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.

