Fitbit integration

How to integrate with the Fitbit API: ROOK simplifies access to Fitbit wearable data for health, fitness, and insurance apps.

Fitbit to Fitbit cloud to ROOK Connect to Your backend: how Fitbit data reaches your product through ROOK.

How it connects

ROOK connects to Fitbit through its cloud API.

Fitbit is now called Google Health. ROOK's Fitbit Web API integration delivers body metrics, physical activity and sleep data from Fitbit devices as structured JSON, by webhook and API.

Our Fitbit integration delivers notifications within minutes after a user completes an event and syncs their app.

Read the Fitbit docs
ROOK Connectphysical_summary · JSON
{  "data_structure": "physical_summary",  "user_id": "demo-user-01",  "physical_health": { "summary": { "physical_summary": {    "metadata": {      "sources_of_data_array": ["Fitbit"]    },    "distance": {      "steps_int": 8432,      "active_steps_int": 6120,      "walked_distance_meters_float": 6180.0    },    "activity": { "active_seconds_int": 3240 }  } } }}
ROOK Connectsleep_summary · JSON
{  "data_structure": "sleep_summary",  "user_id": "demo-user-01",  "sleep_health": { "summary": { "sleep_summary": {    "metadata": {      "sources_of_data_array": ["Fitbit"]    },    "duration": {      "sleep_duration_seconds_int": 26400,      "deep_sleep_duration_seconds_int": 6300,      "rem_sleep_duration_seconds_int": 5400    },    "heart_rate": { "hr_resting_bpm_int": 56 }  } } }}
ROOK Connectbody_summary · JSON
{  "data_structure": "body_summary",  "user_id": "demo-user-01",  "body_health": { "summary": { "body_summary": {    "metadata": {      "sources_of_data_array": ["Fitbit"]    },    "heart_rate": {      "hr_avg_bpm_int": 67,      "hr_resting_bpm_int": 58    },    "oxygenation": { "saturation_avg_percentage_int": 97 }  } } }}

Available data

The Fitbit data ROOK delivers.

Every field below comes from the Fitbit documentation and arrives in ROOK's standard structure, whatever device the user wears.

Physical health

physical summary25 fields

  • active_seconds_int
  • calories_basal_metabolic_rate_kcal_float
  • calories_expenditure_kcal_float
  • calories_net_active_kcal_float
  • elevation_gain_actual_altitude_meters_float
  • elevation_granular_data_array
  • elevation_loss_actual_altitude_meters_float
  • floors_climbed_granular_data_array
  • floors_climbed_float
  • hr_avg_bpm_int
  • hr_granular_data_array
  • hr_maximum_bpm_int
  • hr_minimum_bpm_int
  • hr_resting_bpm_int
  • hrv_avg_rmssd_float
  • low_intensity_seconds_int
  • moderate_intensity_seconds_int
  • rest_seconds_int
  • steps_granular_data_array
  • steps_int
  • swimming_num_strokes_float
  • traveled_distance_granular_data_array
  • traveled_distance_meters_float
  • vigorous_intensity_seconds_int
  • vo2max_mL_per_min_per_kg_int

activity event26 fields

  • active_seconds_int
  • activity_duration_seconds_int
  • activity_end_datetime_string
  • activity_start_datetime_string
  • activity_type_name_string
  • calories_expenditure_kcal_float
  • elevation_gain_actual_altitude_meters_float
  • elevation_granular_data_array
  • floors_climbed_granular_data_array
  • floors_climbed_float
  • hr_avg_bpm_int
  • hr_granular_data_array
  • hr_maximum_bpm_int
  • hr_minimum_bpm_int
  • hr_resting_bpm_int
  • low_intensity_seconds_int
  • moderate_intensity_seconds_int
  • pace_avg_min_per_km_float
  • rest_seconds_int
  • speed_avg_meters_per_second_float
  • steps_granular_data_array
  • steps_int
  • swimming_num_strokes_float
  • traveled_distance_granular_data_array
  • traveled_distance_meters_float
  • vigorous_intensity_seconds_int

steps event1 field

  • accumulated_steps_int

Sleep health

sleep summary19 fields

  • breaths_avg_per_min_int
  • deep_sleep_duration_seconds_int
  • hrv_avg_rmssd_float
  • hrv_rmssd_granular_data_array
  • light_sleep_duration_seconds_int
  • rem_sleep_duration_seconds_int
  • saturation_avg_percentage_int
  • saturation_granular_data_array
  • saturation_maximum_percentage_int
  • saturation_minimum_percentage_int
  • sleep_date_string
  • sleep_duration_seconds_int
  • sleep_efficiency_1_100_score_int
  • sleep_end_datetime_string
  • sleep_start_datetime_string
  • temperature_delta_object
  • time_awake_during_sleep_seconds_int
  • time_in_bed_seconds_int
  • time_to_fall_asleep_seconds_int

Body health

body summary13 fields

  • bmi_float
  • calories_intake_kcal_float
  • carbohydrates_intake_g_float
  • fat_intake_g_float
  • fiber_intake_g_float
  • protein_intake_g_float
  • sodium_intake_mg_float
  • temperature_avg_object
  • temperature_granular_data_array
  • temperature_maximum_object
  • temperature_minimum_object
  • water_total_consumption_mL_int
  • weight_kg_float

Get started

Connect Fitbit in three steps.

  1. Enable Fitbit in the ROOK portalTurn Fitbit on as a data source for your client in the ROOK portal.
  2. Add Fitbit to your connections pageUsers pick Fitbit on the connections page and authorize ROOK with their Fitbit account.
  3. Receive standardized dataROOK turns Fitbit data into the same JSON structure as every other data source and delivers it to your backend by webhook and API.

Use cases

What teams build with Fitbit data.

From seamless wearable integrations to advanced health insights, ROOK empowers you to build personalized wellness apps, research platforms, fitness dashboards, chronic care solutions and many more great use cases.

More data sources

More data sources ROOK connects to through their cloud APIs.

FAQ

Frequently asked questions about the Fitbit integration

What teams ask before they connect Fitbit through ROOK.

What Fitbit data can I get through ROOK?

ROOK extracts 84 Fitbit fields covering physical activity, sleep and body and vital signs data, grouped into summaries and events. The data each user shares depends on the permissions they grant when they connect Fitbit.

How quickly does Fitbit data reach my backend?

Our Fitbit integration delivers notifications within minutes after a user completes an event and syncs their app.

Do I need my own Fitbit developer account?

No. ROOK handles the Fitbit connection, so you only enable Fitbit as a data source in the ROOK portal.

How does ROOK connect to Fitbit?

Through the Fitbit cloud API. Users authorize their Fitbit account once and ROOK keeps pulling new data, with no mobile development on your side.

Read the Fitbit documentation
Still have questions?Our team can review your sources and use case with you.
Schedule a demo

Articles on Fitbit from the ROOK blog

Build on better health data

Turn fragmented health data into your next product advantage.

Connect the sources your users rely on, standardize what comes back, and build workflows that respond to change.

Newsletter

Stay in the loop.

Sign up with your email address to receive news and updates from the ROOK team.

We respect your privacy. Read our privacy policy.