One integration
Integrate one API instead of one per vendor, and cut the development time of every new source.
A unified health data API for wearables and devices
ROOK Connect is ROOK's health data API: one connection to wearables, glucose monitors and sensors, with normalized data delivered by webhook or API.
What one API handles
One integration replaces a stack of vendor connections
ROOK gives developers a simple, reliable integration with SDKs and detailed documentation, so your team builds health features instead of maintaining connectors.
Normalized data
Fragmented vendor formats arrive standardized and structured, ready for analysis.
500+ devices
Apple, Google, Fitbit, Garmin, Oura, Samsung and more, so your platform grows without new integrations.
API and webhooks
Receive normalized data through webhooks as soon as the device syncs, or query it through the API.
Sandbox environment
Try the integration end to end in a testing environment before you go to production.
Built for compliance
ROOK operates under a HIPAA-aligned security program, signs BAAs with covered entities, and processes EU personal data under GDPR as a data processor.
Supported devices
The devices your users already wear
A curated selection of the most requested integrations. The full catalog covers wearables, glucose monitors, scales, sleep trackers and BLE devices.
One schema
Every device arrives in the same structure
Oura's REST API, Apple's HealthKit or Garmin's webhooks: ROOK normalizes all of it into one consistent schema, so your code reads a sleep summary the same way whatever device recorded it.
Oura REST API
Polled from the cloud with OAuth, in Oura’s own JSON schema.
Apple HealthKit
Read on the iPhone through the SDK, as HealthKit samples.
Garmin webhooks
Pushed by Garmin as FIT-derived JSON.
ROOK Connectfrom the Oura REST API · sleep_summary
{ "data_structure": "sleep_summary", "user_id": "demo-user-01", "sleep_health": { "summary": { "sleep_summary": { "metadata": { "sources_of_data_array": ["Oura"] }, "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 Connectfrom Apple HealthKit · sleep_summary
{ "data_structure": "sleep_summary", "user_id": "demo-user-01", "sleep_health": { "summary": { "sleep_summary": { "metadata": { "sources_of_data_array": ["Apple Health"] }, "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 Connectfrom Garmin webhooks · sleep_summary
{ "data_structure": "sleep_summary", "user_id": "demo-user-01", "sleep_health": { "summary": { "sleep_summary": { "metadata": { "sources_of_data_array": ["Garmin"] }, "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 } } } }}One API or three
Why one API beats three vendor integrations
Each vendor ships its own authentication, payload shape and update cadence. ROOK absorbs the differences, so your team writes the integration code once.
| Capability | Apple HealthiOS SDK | Oura RingREST API | GarminREST + webhooks | With ROOKOne integration |
|---|---|---|---|---|
| Authentication | On-device (HealthKit) | OAuth 2.0 | OAuth 1.0a | Single OAuth, handled |
| Data format | HKSample, proprietary | JSON, Oura schema | JSON, FIT-derived | Unified ROOK schema |
| Update cadence | Real time, on read | Hourly polling | Push (webhook) | Normalized webhooks |
| Historical window | Up to device limit | Full account history | Last 90 days | Backfill on connect |
| Maintenance | Yours | Yours | Yours | Handled by ROOK |
Industries
Wearable data that powers products across industries
ROOK's integrations and recommendations are the foundation for companies that unlock health data, streamline workflows and build better solutions.
01Fitness and wellness
Activity tracking, deeper insights and gamified experiences that keep users engaged.
02Healthcare
Remote monitoring and early intervention between visits.
03Insurance
Personalized underwriting and incentive programs built on real activity.
04Corporate wellness
Wellbeing programs and challenges that reward healthier habits at work.
05Pharma
Continuous real-world data collection for studies and patient programs.
06Every use case
See how teams across industries build on ROOK, with use cases and case studies.
Since 2022
From gym heart rate monitors to a health data API
Founded in 2022, ROOK partners with companies in digital health, fitness and InsurTech, with a team experienced in health data and software engineering.
A heart rate platform for gyms
ROOK started as a heart rate monitoring platform that connected coaches and gyms with their users.
A better way to connect health data
We saw the need for a better way to connect apps and health data, and to make meaningful inputs accessible.
From fitness to healthcare and insurance
What began in fitness now powers healthcare, insurance, wellness, gaming and more.
A B2B API for health data
Today ROOK is a B2B company whose API turns health data and insights into new opportunities.
Documentation
Everything you need to start your integration
Step-by-step technical documentation to get your ROOK integration running and compatible with any wearable.
Articles on unified health data APIs from the ROOK blog
- What is a unified health API, and how does it help personalization?A unified API connects wearables and health apps through one integration, so health and fitness platforms get one data flow for personalization.Read more
- Why is wearable data messy, and how do you normalize it with one API?Wearable data varies in format, structure and accuracy across devices. A unified API translates it into one consistent format for health apps.Read more
- Why Integrate Hundreds of Wearables Through a Single API?Integrating each wearable separately means many SDKs, formats and updates. A single API consolidates device data into one standardized workflow.Read more
Nothing matches that search.
Build on better health data
Imagine what you can build with ROOK.
Connect the sources your users rely on, standardize what comes back, and build workflows that respond to change.
FAQ
Frequently asked questions about the ROOK API
Getting started, the components to integrate, pricing and compliance.
How do I get started with ROOK?
Create a portal account and follow the guided setup, then read the technical documentation. The ROOK Handbook helps you organize the integration project.
Create an accountWhich components should I integrate?
To get the most out of ROOK, integrate these core components:
- Connection Page so users connect their wearables easily
- Webhook to receive data updates as they arrive
- SDKs or ROOK App for sources that live on the phone
- ROOK Score for optional engagement scores and health insights
Which industries use ROOK?
Health and wellness apps use it for activity tracking and engagement, insurers for personalized underwriting and incentives, healthcare providers for remote monitoring, and fitness platforms for deeper insights and gamified experiences.
View use casesHow much does ROOK cost?
Pricing depends on your plan, usage volume and the products or add-ons you need. For unique requirements or large-scale needs, the ROOK team can tailor a solution.
See pricingIs ROOK HIPAA and GDPR compliant?
ROOK operates under a HIPAA-aligned security program, signs BAAs with covered entities, and processes EU personal data under GDPR as a data processor.
Review security and complianceNo questions match that yet. Try another word or topic.
Still have questions?Our team can review your sources and use case with you.
Schedule a demo