Permissions Guide

Overview

Applications and clock faces developed for Fitbit OS must be granted permissions by the user, in order to use specific Device and Companion APIs.

The permissions system is primarily provided to inform users which apps are using which functionality of the system, and allow them to make informed decisions about whether they want to prevent its installation.

If a developer tries to utilize an API without first requesting the appropriate permission, the API will generate an error message, and the requested data will not be returned.

Available Permissions

The list of available permissions are as follows:

Activity

Read user activities for today (distance, calories, steps, elevation and active minutes), and daily goals.

Related API: Device.User-activity.

User Profile

Read non-identifiable personal information (gender, age, height, weight, resting heart rate, basal metabolic rate, stride, heart rate zones).

Related API: Device.User-profile.

Heart Rate

Application may read the heart-rate sensor in real-time.

Related API: Device.Heart-rate.

Location

Application and companion may request location data from the device or mobile GPS.

Related APIs: Device.Geolocation, Companion.Geolocation.

Internet

Companion may communicate with the Internet using your phone data connection.

Related API: Companion.Fetch

Run in background

Companion may run even when the application is not actively in use.

Related APIs: Companion.Location-change, Companion.Wake-interval

Requesting Permissions

In order to request permission to use specific APIs, they just need to open their project's package.json file in Fitbit Studio, then tick the appropriate permissions.

When the application is installed, the user will be prompted to accept the permission requests.