Get Lifetime Stats
chevron down
 

Get Lifetime Stats

Retrieves the user's activity statistics.

Scope: activity


Request

GET /1/user/[user-id]/activities.json

URI Arguments
user-id required The encoded ID of the user. Use "-" (dash) for current logged-in user.

Request Headers
authorization required Specify the token type and Fitbit user’s access token.
Token type: Bearer
accept optional The media type of the response content the client is expecting.
Supported: application/json
accept-language optional The measurement unit system to use for response values. See Localization.
accept-locale optional The locale to use for response values. See Localization.

Examples
curl -X GET "https://api.fitbit.com/1/user/-/activities.json" \
-H "accept: application/json" \
-H "authorization: Bearer <access_token>"


Response

Element Name Description
best : total : distance : date The date the user's best distance was achieved.
best : total : distance : value The user's best distance achieved. This includes tracker and manual activity log entries.
best : total : floors : date The date the user's best floors was achieved.
best : total : floors : value The user's best floors achieved. This includes tracker and manual activity log entries.
best : total : steps : date The date the user's best step count was achieved.
best : total : steps : value The user's best step count achieved. This includes tracker and manual activity log entries.
best : tracker : distance : date The date the user's best distance was achieved. This includes tracker data only.
best : tracker : distance : value The user's best distance achieved. This includes tracker data only.
best : tracker : floors : date The date the user's best floors was achieved. This includes tracker data only.
best : tracker : floors : value The user's best floors achieved. This includes tracker data only.
best : tracker : steps : date The date the user's best step count was achieved. This includes tracker data only.
best : tracker : steps : value The user's best step count achieved. This includes tracker data only.
lifetime : total : activeScore Functionality removed. A response is returned for backward compatibility.
Supported: -1
lifetime : total : caloriesOut Functionality removed. A response is returned for backward compatibility.
Supported: -1
lifetime : total : distance The total distance recorded over the lifetime of the user's account. This includes tracker and manual activity log entries.
lifetime : total : floors The total floors recorded over the lifetime of the user's account. This includes tracker and manual activity log entries.
lifetime : total : steps The total steps recorded over the lifetime of the user's account. This includes tracker and manual activity log entries.
lifetime : tracker : activeScore Functionality removed. A response is returned for backward compatibility.
Supported: -1
lifetime : tracker : caloriesOut Functionality removed. A response is returned for backward compatibility.
Supported: -1
lifetime : tracker : distance The total distance recorded by the tracker over the lifetime of the user's account.
lifetime : tracker : floors The total floors recorded by the tracker over the lifetime of the user's account.
lifetime : tracker : steps The total steps recorded by the tracker over the lifetime of the user's account.
{
  "best": {
    "total": {
      "distance": {
        "date": "2016-07-17",
        "value": 28.69259
      },
      "floors": {
        "date": "2018-05-28",
        "value": 73.00000011096
      },
      "steps": {
        "date": "2016-07-17",
        "value": 38826
      }
    },
    "tracker": {
      "distance": {
        "date": "2016-07-17",
        "value": 28.69259
      },
      "floors": {
        "date": "2018-05-28",
        "value": 73.00000011096
      },
      "steps": {
        "date": "2016-07-17",
        "value": 38826
      }
    }
  },
  "lifetime": {
    "total": {
      "activeScore": -1,
      "caloriesOut": -1,
      "distance": 8302.5,
      "floors": 10278,
      "steps": 11152512
    },
    "tracker": {
      "activeScore": -1,
      "caloriesOut": -1,
      "distance": 8288.26,
      "floors": 10278,
      "steps": 11133281
    }
  }
}
      

Response Headers
content-type The media type of the response content being sent to the client.
Supported: application/json
fitbit-rate-limit-limit The quota number of calls.
fitbit-rate-limit-remaining The number of calls remaining before hitting the rate limit.
fitbit-rate-limit-reset The number of seconds until the rate limit resets.

Note: The rate limit headers are approximate and asynchronously updated. This means that there may be a minor delay in the decrementing of remaining requests. This could result in your application receiving an unexpected 429 response if you don't track the total number of requests you make yourself.

Response Type

HTTP Status Code HTTP response code. List of codes are found in the Troubleshooting Guide.
Status Message Description of the status code.
Response Body Contains the JSON response to the API call. When errors are returned by the API call, the errorType, fieldName and message text will provide more information to the cause of the failure.

Response Codes
200 A successful request.
400 The request had bad syntax or was inherently impossible to be satisfied.
401 The request requires user authentication.

Note: For a complete list of response codes, please refer to the Troubleshooting Guide.

Additional Information

The data is returned in the format requested using units in the unit system which corresponds to the Accept-Language header provided.

Activity statistics includes Lifetime and Best achievement values from the My Achievements tile on the website dashboard. Response contains both statistics from the tracker device and total numbers including tracker data and manual activity log entries as seen on the Fitbit website dashboard.

The Fitbit user's My Achievements (Friends or Anyone) privacy permission grants access to user's resource.

Distance

Devices that support on-device or connected GPS will record distance when the exercise is initiated using the on-device Exercise application. For auto-detected exercises, we use steps and the stride length of the user to estimate distance. To determine how the exercise was recorded, see the Get Activity Log List response element "logType".