Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

GET Actvity Logs List - HR Zones Availability

ANSWERED

Hello,

 

Recently, we are seeing 'Activity Logs List' records w/o the HR Zones. Such as;

 

{
      "activeDuration": 2155000,
      "activityLevel": [
        {
          "minutes": 0,
          "name": "sedentary"
        },
        {
          "minutes": 0,
          "name": "lightly"
        },
        {
          "minutes": 1,
          "name": "fairly"
        },
        {
          "minutes": 35,
          "name": "very"
        }
      ],
      "activityName": "Elliptical",
      "activityTypeId": 20047,
      "calories": 267,
      "caloriesLink": "https://api.fitbit.com/1/user/-/activities/calories/date/2016-07-22/2016-07-22/1min/time/8:21/8:57.json",
      "duration": 2155000,
      "heartRateLink": "https://api.fitbit.com/1/user/-/activities/heart/date/2016-07-22/2016-07-22/1sec/time/08:21:10/08:57:05.json",
      "lastModified": "2016-07-22T07:55:21.000Z",
      "logId": FILTERED,
      "logType": "auto_detected",
      "manualValuesSpecified": {
        "calories": false,
        "distance": false,
        "steps": false
      },
      "startTime": "2016-07-22T08:21:10.000+02:00",
      "steps": 3360,
      "tcxLink": "https://api.fitbit.com/1/user/-/activities/FILTERED.tcx"
    }

 

Can anyone tell me 'when' does HR Zones actually does becomes available? Or the screnario/state when it does? Such as the Device in use, "logType", Activity type, etc.

 

Thanks in advance!

 

Cheers!

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions

@Rapido thanks for calling this out here! This should be fixed now and the endpoint should behave normally moving forward. This was an issue on our end.

 

Apologies for the inconvenience!

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

I'm hoping this is just a bug on Fitbit's end, but I also noticed it was no longer returning the heart rate fields.

 

Activities which I previously got from this list, and had HR information then, now don't include it when I get this endpoint.

Best Answer
0 Votes

@Rapido thanks for calling this out here! This should be fixed now and the endpoint should behave normally moving forward. This was an issue on our end.

 

Apologies for the inconvenience!

Best Answer
0 Votes