Get Frequent Activities
chevron down

Get Frequent Activities

Retrieves a list of a user's frequent activities.

Scope: activity


GET /1/user/[user-id]/activities/frequent.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.

curl -X GET "[user-id]/activities/frequent.json" \
-H "accept: application/json" \
-H "authorization: Bearer <access_token>"


Element Name Description
activityId The recorded activity’s identifier number. For example, the activityId for “Run” is 90009. For a complete list of exercise identifiers, see Get All Activity Types endpoint.
calories The number of calories burned associated with the activity.
description Additional information about the recorded activity.
distance Distance traveled associated with the recorded activity.
duration The length in time (milliseconds) after the exercise was edited. This value will contain pauses during the exercise.
name The name of the recorded activity.
    "activityId": 90013,
    "calories": -1,
    "description": "Walking less than 2 mph, strolling very slowly",
    "distance": 1.61,
    "duration": 1178000,
    "name": "Walk"
    "activityId": 15000,
    "calories": 0,
    "description": "",
    "distance": 0,
    "duration": 1228000,
    "name": "Sport"

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 response if provided in the format requested using units in the unit system which corresponds to the Accept-Language header provided.

A frequent activity record contains the distance and duration values recorded during the last time the activity was logged. The record retrieved can be used to log the activity via the Log Activity endpoint with the same or adjusted values for distance and duration.