ROOK add-ons: more capabilities, only when they're needed
Optional ROOK Connect capabilities, such as historical data, webhook security, and granular data, that activate without changing the integration.
How they work
ROOK add-ons activate on top of the existing integration
Each add-on is enabled on the ROOK account, with no new integration to build.
Choose an add-on
Each add-on addresses a specific product need.
Activate it on your account
It is enabled on the ROOK account, with no new integration to build.
Use it in your data
The capability becomes available in the data, the webhook, or the app, depending on the add-on.
Add-on catalog
Available ROOK add-ons
Each add-on is tagged with the products it works with. Pick one to see what it adds and who it is for.
- Callback URLEvery user returns to the app as soon as they finish connecting.
- Pre-Existing DataData from the first moment, not from tomorrow.
- Notifications WebhookKnow what's happening in the integration, as it happens.
- Multiple accounts & InstancesOne organization, several independent operations.
- Basic auth & Okta tokenOnly authorized requests reach the endpoints.
- Data source proprietary & unstructured dataEach brand's exclusive metrics, available too.
- Continuous steps eventsThe day's activity, hour by hour.
- Granular dataMore detail behind every summary.
- White label appROOK App, with each company's brand.
- Medical Device MetadataEvery reading carries the device that took it.
- Clinical Ready (FHIR R4)Health data in the format clinical systems read.
- Branded AuthConnection screens with each company's brand.
Callback URL
Every user returns to the app as soon as they finish connecting.
Once users finish connecting a source, they are automatically redirected back to the client's application. The flow stays continuous, and users don't get lost along the way.
Ideal for: Products that care about every step of onboarding.
Three phone screens in a row: a generic app with a “Connect your wearable” button, a source authorization screen asking to “Allow access to your data,” and the same app again with a check mark and “Connection successful.” The arrow back to the app is labeled Callback URL. Pre-Existing Data
Data from the first moment, not from tomorrow.
When a source is connected, ROOK retrieves the user's recent history from it. The product can show information, calculate scores, and drive engagement from day one, without waiting for new records.
Ideal for: Products that need to show value from onboarding.
A timeline of the days before the connection day. With Pre-Existing Data, those days already hold activity bars; without it, the same days are empty. Notifications Webhook
Know what's happening in the integration, as it happens.
Teams receive alerts when users connect or disconnect sources and when events occur in the integration. That way they can catch issues before they affect the experience and keep the data flow under control.
Ideal for: Product and support teams that need visibility into operations.
A notification tray with three alerts: “User 1042 connected Garmin,” just now; “User 0871 disconnected Oura,” 2 minutes ago; and “New data sync completed,” 5 minutes ago. Multiple accounts & Instances
One organization, several independent operations.
Each client, brand, or region can have its own account and instance within ROOK, with separate configuration and data. It's the foundation for scaling to multiple clients without mixing operations.
Ideal for: Platforms that serve multiple clients or manage different brands.
ROOK connected to one organization account that branches into three instances, labeled Client, Brand and Region, each with its own configuration and its own data. Basic auth & Okta token
Only authorized requests reach the endpoints.
An extra layer of security for the webhook. Only requests authenticated with Basic Auth or Okta tokens reach the client's endpoints, helping each organization comply with its security policies.
Ideal for: Companies with corporate security requirements or IT review processes.
A flow from ROOK through a padlock labeled Basic Auth · Okta to the client endpoint: a request with a token passes along a solid line, and a request without a token stops at the padlock. Data source proprietary & unstructured data
Each brand's exclusive metrics, available too.
In addition to standardized data, ROOK delivers each manufacturer's proprietary metrics, such as Oura's Readiness Score or Garmin-specific metrics. It's enabled per data source, so the product adds only what it will use.
Ideal for: Products whose users value the scores from their favorite brand.
A standardized data card with steps, sleep duration and resting heart rate, plus a second card with a Brand metric badge showing a Readiness Score of 82. Continuous steps events
The day's activity, hour by hour.
Instead of waiting for the daily summary, the product receives step events every hour. That makes it possible to respond during the day with challenges, reminders, or goals in progress.
Ideal for: Fitness apps and wellness programs built around activity challenges.
An hourly bar chart of steps from 6:00 to 18:00 with a running total that crosses the 8,000-step daily goal at 15:00, next to a single gray block for the daily summary only. Granular data
More detail behind every summary.
Detailed metrics that complement daily summaries. Teams see how a metric evolved throughout the day, not just its final value, for deeper analysis.
Ideal for: Analytics, research, or advanced personalization teams.
A daily summary card reading Average heart rate · 72 bpm, with a magnifying glass revealing the full heart rate curve of the day. Summary: one number. Granular: the full story. White label app
ROOK App, with each company's brand.
The app launches with each company's name, logo, and primary color. ROOK generates a complementary palette so the experience looks consistent from start to finish, without building a custom app.
Ideal for: Companies that want their own mobile experience from day one.
Two phones with the same connections screen: one in ROOK's neutral palette, and one white-labeled for an invented sample brand in deep blue, with the palette generated from that primary color. Medical Device Metadata
Every reading carries the device that took it.
Readings arrive with the manufacturer, model and type of the device, and how the data reached ROOK. Regulatory information is added when it is available, so clinical teams know where each value came from.
Ideal for: Care programs that need to trace every reading back to its device.
A blood pressure reading of 118/76 mmHg linked to a device card that lists manufacturer, model, device type and source type. Clinical Ready (FHIR R4)
Health data in the format clinical systems read.
ROOK turns normalized health summaries into FHIR R4 documents with LOINC codes and UCUM units, and delivers them through the same webhook each time a summary is generated or updated.
Ideal for: Teams that send wearable data into EHRs, EMRs or other clinical systems.
A ROOK summary card with steps and resting heart rate, an arrow labeled FHIR R4, and a FHIR Observation card with a LOINC code, a value and a UCUM unit. Branded Auth
Connection screens with each company's brand.
ROOK's visual identity is removed from the data source connection screens and replaced with the company's own, so users connect their devices inside an experience that looks native from start to finish.
Ideal for: Companies that want every onboarding screen under their own brand.
Two connection screens side by side: one with the ROOK logo, and one with an invented sample brand logo in its place.
- CorePurchased separately
- Core+3 of choice included
- BusinessAll included
- EnterpriseAll included
Add-ons
ROOK Connect, plus only the add-ons each product needs
Activate only the capabilities that add value at each stage of the product.
Read more in our technical documentationFAQ
Frequently asked questions about ROOK add-ons
How add-ons activate, which plans include them, and what each one adds.
What are ROOK add-ons?
ROOK add-ons are optional capabilities for ROOK Connect, such as historical data, webhook security and granular data. They add more data, more security and more control without changing the integration.
Do I need to build a new integration to use an add-on?
No. Each add-on is enabled on the ROOK account and works on top of the existing integration, so there is no new integration to build.
Which add-ons are free?
Callback URL and Pre-Existing Data are free on every plan.
Which plans include add-ons?
Business and Enterprise include every add-on. Core purchases them separately, and Core+ picks them as part of its 3 included products or add-ons.
See pricingHow much past data does Pre-Existing Data retrieve?
It depends on how the source connects. Mobile sources read through the ROOK SDKs reach further back than API-based sources such as Garmin or Oura. The technical documentation lists the current range for each.
Read the Pre-Existing Data documentationHow does ROOK secure webhook deliveries?
The Basic auth & Okta token add-on makes sure only requests authenticated with Basic Auth or Okta tokens reach the client's endpoints.
Read the add-on docsNo questions match that yet. Try another word or topic.