Activity list at GET /1/activities.json is incomplete?

[martaen]

I'm facing an issue that I don't get some activities via GET /1/activities.json endpoint.
For example, I can get GET /1/activities/91045.json, but when I retrieve full list through GET /1/activities.json, it contains no info on activity 91045. Are there any limitations on GET /1/activities.json ?

I see the topic https://community.fitbit.com/t5/Web-API-Development/Activity-List-incomplete/td-p/1141907, but it dates back to 2016, I'd love to know the current state.

[JohnFitbit]

Hi @martaen,

This is a great question, and I'm not quite sure myself. I reproduced it and I was also not able to pull up 91045 in the json response for the browse activity endpoint, despite it being a public level activity.

I'm going to file a ticket with engineering to get more information. In the meantime, please let me know if you find any other activities that don't show up in the browse activities response.

[martaen]

Hi John, I went through the activities that we are trying to fetch and I think I have the same issue with the following activities:

1072, 3100, 3101, 3102, 3103, 3104, 4001, 5020, 8095, 8245, 11040, 16010, 16030, 59001, 91040, 91041, 91042, 91043, 91044, 91045, 91046, 91047, 91051, 91052, 91053, 91054, 91055, 91056, 91057, 91059.

For me, they all are accessible with GET /1/activities/{id}.json, but not visible in GET /1/activities.json. 

[JohnFitbit]

@martaen I received word from engineering and this is what I found out. Both the GET /1/activities/{id}.json and GET /1/activities.json are actually working by design, however, I will be filing an enhancement request to sync the activity data so that activities will be returned by both endpoints respectively.

Thanks again for raising this, and I'll post here when I hear any upcoming improvements for this endpoint.