03-26-2018 01:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-26-2018 01:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I am working on a Mobile Application on Android that uses FitBit data as Input.
All my calls are functioning as expected, except for one.
The following EndPoint is not returning any data:
GET https://api.fitbit.com/1/user/[user-id]/activities/date/[date].json
Through the Forum I have been pointed to the following call:
GET https://api.fitbit.com/1/user/[user-id]/activities/list.json&afterDate=2018-02-28&offset=0&limit=2&sort=asc”
This call is not featured in the documentation found on the FitBit API documentation, which seems strange. Also it is unclear to me what exactly the variables "afterDate", "offset", "limit" and "sort" mean. Finally, I would like to retrieve parameters from the section "Summary" from the not functioning call.
Some questions about this:
- Are there additional API calls that can be made to the documentation found at "https://dev.fitbit.com/build/reference/web-api/_"?
- Is there an additional document which describes parameters mentioned above in detail? If so, can you please point me to it?
Please advice..
03-26-2018 10:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-26-2018 10:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
Hello @NielsWearables, I'm not sure why the 'https://api.fitbit.com/1/user/[user-id]/activities/date/[date].json' end point isnt working, since I cant get it to work ether.
However the 'activities/list.json' end point is documented here which will explain what the "afterDate", "offset", "limit" and "sort" variables are for.
03-26-2018 12:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-26-2018 12:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks Stuart, must have missed this one..

04-05-2018 04:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

04-05-2018 04:32
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Does anyone from the FitBit team have an answer for this? Can you please check the above API EndPoint? It is not functioning, this should be a concern, no?

