Through the s for guide , the aim is to standardize how technical teams manage document versions within integrations with the ROOK SDK and APIs.

This guide helps ensure reliable communication between client systems and ROOK integration, reducing synchronization errors, incompatibilities, and the use of outdated data during integration processes.

The initiative aims to prevent common errors stemming from improper version control, such as synchronization failures, incompatibilities between environments, and the transmission of outdated data. With proper implementation of , developers can maintain more stable integrations, reduce production issues, and optimize the traceability of collected data.

The acts as a key identifier within ROOK's data structures. Each submitted data structure includes this version, which allows for validation of the delivered JSON version by referencing an update to a previously extracted and delivered data structure.

To avoid these scenarios, ROOK recommends that teams proactively validate and update health data with each new delivery of data structures according to their version.

The following recommendations should be followed when integrating ROOK and using datasets:

These recommendations aim to strengthen the reliability of the integration ecosystem and significantly reduce the risk of operational errors.

It is recommended to record the following in the internal logs:

This facilitates monitoring, debugging, and historical control of changes between versions, allowing for a faster response to incidents or inconsistencies.

To ensure a stable and consistent implementation, it's necessary to validate the integration's behavior under various scenarios. These tests help detect misalignments, update errors, and synchronization issues before going into production.

Correct use of document_version:

If you don't update it, your integration may display outdated or inconsistent data. This often leads to logic errors and problems with the end-user experience.

Ignore it completely. That indicates a misalignment or a resending of old data. The correct thing to do is:

Very simple:

No. The version is generated solely by ROOK to ensure consistency and traceability. Your integration should only receive, store, and forward it.

You will generate corrupt or inconsistent data for the end user.

Each dataset represents a complete snapshot of the user's state: they are not mixed, they are replaced.

You must validate:

For:

We are announcing the launch of the JSON Simulator, a new tool in the ROOK portal designed to simplify and accelerate the validation of integrations with our API and SDK ecosystem.

The JSON Simulator allows teams to simulate, preview, and send real JSON payloads to their configured webhook, without the need for a physical wearable or data generated by end users. The tool integrates directly with the existing configuration of the ROOK portal.

Previously, customers needed an active wearable and had to wait for data generation to validate their webhook. With the JSON Simulator, that bottleneck disappears.

The tool allows you to:

The JSON Simulator reduces integration times, removes dependency on wearables for testing, and improves understanding of how data varies across brands and structures. This enables teams to:

The JSON Simulator is available in the ROOK portal under the Tools module. Customers must have a configured webhook to use it; otherwise, they will be redirected to the configuration area.

It is a tool in the ROOK portal that allows you to generate, preview, and send real JSON payloads to the customer’s Data Webhook, without physical wearables or real user data.

It speeds up and simplifies integration validation with ROOK’s APIs and SDKs. It enables full-flow testing without waiting for real data or relying on devices.

Previously, customers needed an active wearable to validate webhook reception, which caused delays.

With the JSON Simulator, tests are immediate and fully controlled.

You can simulate any JSON available in ROOK’s Version 2 data structure by selecting:

They are real JSONs based on ROOK’s official structure, but they contain a generic user_id that does not affect your KPIs or real data.

Yes. The tool allows you to:

The simulator automatically checks its status.

If it’s inactive, you won’t be able to generate or send JSON. The portal will guide you to activate it.

The simulator respects your active settings, such as granularity and other applicable parameters.

You can generate fully populated JSON payloads without nulls—ideal for testing pipelines, dashboards, or transformations.

Generation and delivery take less than 3 seconds per request.

In the ROOK portal under Tools → JSON Simulator.

Any customer with a Webhook already configured in the portal.

If you don’t have one, the system will automatically redirect you to configure it.

We are currently releasing the update LTS (Long Term Support)of its SDKs, a release focused on the reliability, scalability, and technical maturity of the ROOK SDKs. This update not only improves the experience of syncing and retrieving health data from Health Connect and Apple Health, but also expands support for new sources such as Samsung Health.

The LTS update addresses one of the key pillars of ROOK's technical strategy: ensuring that every integration with health data sources is faster, more robust and predictable.

During this stabilization cycle, we focused on three main objectives:

The new version of the SDK of Health Connect introduces critical improvements to synchronization, offering developers more control and improved data accuracy. The most notable updates are:

These combined improvements increase refresh rate, energy efficiency, and data accuracy, directly impacting the quality of digital health experiences built on ROOK.

The new SDK for Samsung Health is part of the improvements included in this LTS update.

With this release, developers can access activity, sleep, heart rate, body weight, and workout data directly from Samsung Health, without intermediary apps.

The SDK offers:

With this launch, we aim to consolidate our position as an interoperable platform that connects multiple healthcare ecosystems under a single data model, reducing development costs and accelerating time-to-market.

The SDK of Apple Health also receives an update focused on the technical robustness, scalability and traceability of the system. This release aims to improve the internal architecture of the SDK and offer developers a more stable and predictable environment.

Key improvements include:

Together, these enhancements provide a stronger technical foundation, more consistent performance, and more detailed diagnostic capabilities for applications that rely on accurate, continuous health data.

Along with this LTS update, ROOK SDKs will also include updates for the latest versions of mobile frameworks, ensuring a smooth and up-to-date integration:

These updates ensure that developers can integrate ROOK SDKs seamlessly into their latest projects, maintaining stability and compatibility with the most recent releases.

With the stabilization of its SDKs, ROOK reinforces its vision of becoming the standard infrastructure for health and wellness data interoperability.

Each improvement in this version seeks to reduce technical friction, increase the reliability of information and allow companies to build personalized experiences from the biometric data of its users, without worrying about the complexity of each source.

The update LTS (Long Term Support) is a stable release focused on improving the reliability, performance, and scalability of ROOK SDKs. This release includes improvements to Health Connect, Apple Health, and the addition of the new SDK for Samsung Health.

No. However, it's recommended to upgrade to take advantage of performance optimizations, new synchronization methods, and fixes that ensure better data and log handling. Previous versions will continue to work for a limited time, but will no longer receive active support or bug fixes.

This release includes a reduction in the wait time after the health connect request quota to 45 minutes, along with more flexible manual syncs and a new manual sync method that simplifies integration. The optional parameter is also added , which allows you to cancel and reschedule background tasks, as well as local access to synchronized health data and better management of time zones and time records.

The SDK allows direct access to data from activity, sleep, heart rate, body weight, and workouts from Samsung Health, without the need for intermediary apps. It also maintains compatibility with the ROOK data model and supports both manual and automatic synchronization.

The update incorporates the implementation of the Builder design pattern, geared toward a more modular architecture. It also optimizes log collection and delivery, improves system stability and traceability, and internally reorganizes components to facilitate future integrations and maintenance.

Developers will be able to continue using their current integrations without any immediate mandatory changes. However, the new versions offer a more stable foundation and a better development experience, so a gradual migration is recommended.

Full documentation with technical details and implementation examples is available on the ROOK developer portal: https://docs.tryrook.io

Yes, but on a limited basis. Previous versions will receive minimal maintenance for a defined period (see support notes). After that, it's recommended to fully migrate to the LTS version to ensure future compatibility.

ROOK's technical support team is available through the developer support channel or by direct contact at support@tryrook.io.

As part of our commitment to delivering more useful, complete, and customizable health data, ROOK has implemented a new comprehensive data extraction system from connected sources, both API-Based and SDK-Based. This solution enables the use of 100% of the available keys from all integrated data sources.

Until now, data access was limited to a subset of keys, restricting the potential for analysis, personalization, and value generation for end users. Thanks to this enhancement, all available keys have been extracted, inventoried, and organized within our data structure, allowing for a richer and more robust integration.

This new capability drastically reduces the loss of valuable data that was previously unused. The comprehensive extraction system implemented at ROOK allows for:

With this solution in production, the process of integrating new sources becomes more agile, consistent, and transparent. For more information, you can refer to our documentation:

It allows companies to access the full set of data available from each connected source, improving analysis accuracy, user experience personalization, and the ability to generate deeper insights.

It includes all health data collected by wearables and mobile apps. Every metric available at the source can now be extracted and used within ROOK systems.

Currently, all integrated sources are supported, including:

Each extracted key is documented, classified, and standardized to ensure accurate interpretation and use. Additionally, normalization rules are applied to unify measurement units and formats, making it easier to analyze and ensure interoperability across sources.

Yes. This solution is fully designed to integrate with our JSON schemas for events and summaries, ensuring full continuity in data flow without compromising the existing architecture.

Products integrated with ROOK can now access a richer dataset, enabling more complete health and performance analysis.

No. This upgrade is backward-compatible and does not require changes to existing integrations. Expanded key access is automatically available to all clients already consuming data through our current endpoints.

You can visit the API Reference and Data Sources documentation, where you’ll find updates on new keys available in the ROOK data structure, organized by data source.

Samsung Health is coming to ROOK through native SDK for Android, React Native, Flutter & Capacitor (Ionic), enabling direct and reliable access to health data generated by the Samsung Health app. This integration expands ROOK’s coverage within the Android ecosystem.

While Samsung Health can be accessed via Health Connect, this dedicated solution provides greater control over the user experience and the quality of the data. By connecting directly with Samsung’s ecosystem, ROOK can deliver a more tailored, accurate, and continuous integration for Android users.

Thanks to this integration, ROOKConnect users on Android will be able to link their Samsung Health accounts and access health data such as:

The system is also prepared to detect when this data is updated later (as it happens with sleep stages). In such cases, only the relevant changes are sent, ensuring the user always sees the most current information.

The integration is designed to keep data updated throughout the day. Current-day data like sleep is refreshed automatically, and the system can also retrieve data from previous days—without any user action. This ensures a smooth and always up-to-date experience.

If the device was inactive for several days, the system can recover up to 29 days of physical activity events and sleep/body summaries. This ensures that important health information is not lost and gives users a complete view of their wellness.

The current development supported on native Android, React Native, Flutter, and Capacitor available.

Any Android user with the Samsung Health app installed and a compatible device can activate the integration through a ROOKConnect client app.

A wide variety of health data can be synchronized, including:

Synchronization occurs automatically several times a day, especially for sleep. If changes are detected, the data is progressively updated without duplicates. This ensures users always have the most recent and accurate information.

In most cases, no. However, it’s recommended to open the Samsung Health app at least once a week. Samsung automatically syncs with its cloud, and the ROOK SDK can read this data without user interaction. In some models, enabling Samsung Cloud sync may be helpful.

The system can retrieve up to 29 days of physical activity and sleep data when the user opens the app again. This prevents data loss even if the device was inactive for a while.

Samsung stores certain values (like glucose or weight) in different internal units and converts them automatically. This can cause slight variations in the final numbers. ROOK applies rounding to make sure values closely match what users expect to see.

Samsung doesn’t always classify workout types immediately or accurately. In such cases, ROOK displays the data as it was received from Samsung.

If a workout is paused for more than 10 minutes, a new event is generated. If the pause is shorter, ROOK treats it as an update to the original event.

No. Health Connect remains a valid integration path. However, this direct integration with Samsung allows for a more precise, real-time, and Samsung-specific data experience.

The SDK triggers an automatic synchronization every 3 hours, even if the user isn’t using the app. This ensures regular data collection throughout the day.

Not necessarily. Synchronization depends on Android's operating system policies, such as Doze and App Standby, so the process may not occur instantly.

In most cases, no. The SDK is designed to continue working in the background even with battery saver enabled. However, behavior can vary depending on the phone model and system settings.

No. Manual actions don’t affect the automatic sync schedule. The SDK will continue syncing every 3 hours from the last successful synchronization.

If an event or data point wasn’t collected during a sync, the SDK will attempt to retrieve it in the next cycle, provided it’s still available in Samsung Health and hasn’t been filtered out by ROOK’s internal rules.

This project focuses on optimizing the authorization endpoint for data sources in ROOK. The new version, , replaces the previous version , which returned a flat response with simple boolean values.

The redesigned version delivers a richer and more visually informative structure, aimed at improving the experience for both developers and end users. The response now includes:

This enhanced endpoint allows for more dynamic, intuitive, and user-friendly interfaces, making it easier to visualize which wearables or health apps are currently connected.

It’s an API resource that allows you to check whether a user has authorized health or wellness data sources such as wearables or apps (e.g., Fitbit, Garmin, Apple Health).

: required string (unique identifier of the user)

A list of objects representing each enabled source, including its authorization status and an image for UI rendering.

This project aims to allow customers to customize the complementary properties of their integration through the ROOK portal, automating the configuration processes. The main goal is for customers to make changes autonomously and immediately, without the need for support intervention. This will speed up the implementation of changes in their configurations.

The feature introduces an automated configuration management system within the ROOK portal. Customers will have access to an intuitive interface to make real-time adjustments. Available features include the ability to add or edit URLs for webhook notifications, set time zones, enable or disable granular data, and activate security protocols. Each action will be fully audited to ensure traceability.

This system will allow customers to manage their configurations quickly and efficiently, eliminating unnecessary wait times. Automating these processes will provide them with the flexibility to adapt the product to their needs.

The Customize ROOK module will include three main categories:

It is a new feature that allows customers to modify and manage configurations without the need for manual intervention from the support team.

Yes, this feature will be available to all ROOK customers. However, keep in mind that the modules you configure will be available based on your plan and contract. If you'd like to activate a module, please contact ROOK support.

Yes, customers can edit and update their configurations at any time within the portal.

When ROOK extracts health data, the information often comes in raw form and without a clear structure. This phenomenon is known as unstructured data, and it represents one of the biggest challenges (and opportunities) for ROOK.

Unstructured data is any information that does not follow a fixed or predictable format. It is not organized in rows or columns, and often appears as free text or custom fields where each manufacturer decides how to report it.

ROOK takes this unstructured data, interprets it, and transforms it into a standardized, ready-to-use structure. Essential data, such as sleep duration, heart rate, or glucose levels, is converted into clean, consistent fields.

This way, ROOK allows developers and companies to connect multiple data sources without worrying about odd formats or inconsistencies. It enables more effective work with health data without having to interpret each source individually.

ROOK makes both structured and unstructured data available to users, depending on the client’s needs. To enable unstructured data in event and summary JSONs, please check your plan or contact ROOK Support.

Unstructured data will be delivered by ROOK via the respective JSONs, depending on the event or summary it comes from. In this case, we’ll use an example of unstructured data from a Physical Summary extracted from Garmin.

Through this article, ROOK aims to define the interpretation of ROOKScore. This classification is designed to offer users a clearer and more intuitive understanding of their overall well-being through ROOKScore and its associated health pillars.

This new approach introduces performance levels based on percentage ranges, which allows individuals to better interpret their health data and identify areas for improvement:

These levels will be reflected in all ROOKScore indicators, including the pillars of sleep, physical health, and body health, providing a consistent framework to assess progress and set achievable goals. By adding these intuitive scoring levels, we help users take practical steps to improve their health, while also making the data more accessible and motivating.

ROOKScore is a tool that measures your overall well-being through different health pillars, such as sleep, physical health, and body health. This score is calculated using health data.

We have implemented these levels to make ROOKScore results more understandable and accessible. Now, users can easily see what range they fall into and which areas need improvement to reach optimal health.

Results are classified into the following ranges:

These levels reflect your overall performance in the health pillars, such as sleep, physical health, and body health.

Each of the health pillars (sleep, physical, and body) will receive a rating based on the same percentage ranges. This allows the user to see not only their overall score but also which specific areas they should focus on to improve their well-being.

To improve ROOKScore, it is recommended to focus on the pillars where a low score was obtained. This may include improving sleep quality, increasing physical activity, or adopting healthier habits overall. The key is to take practical and consistent steps towards achieving a higher score.

By understanding more clearly and simply where you stand in each health pillar, you will be able to make informed decisions and set realistic goals to improve your overall well-being. Additionally, motivation increases when you can see tangible progress toward an "Excellent" health status.

Not at this time. Clients will be able to implement this interpretation directly.

ROOK is developing an optimization for Granular Data a new feature designed to provide clients with more detailed and standardized information.

Many companies working with health data require precise and consistent information. Until now, Granular Data from different sources arrived at varying times, leading to inconsistencies in analysis and making data-driven decision-making more challenging.

Granular Data allows clients to customize the reception of information

With Granular Data, clients and their users will access more reliable health information, facilitating the development of innovative products and insights.

Our goal is to deliver more useful and accurate data, allowing clients to focus on what truly matters: Innovation and strategic decision-maker.

Granular Data Standardization is a ROOK feature that ensures data from various health sources (Such as Garmin, Apple Health, Health Connect) is aligned within a unified time frame, reducing empty values and duplicates for more consistent and reliable insights.

Health data is received at different intervals and formats depending on the sources, leading to inconsistencies in analysis. Standardization ensures greater accuracy, making data easier to interpret and enhancing the end-user experience.

Temporal standardization adjusts data to arrive at a consistent interval. For instance, if one source sends data every 5 seconds and another every 20 seconds, intermediate values can be estimated using averaging or artificial intelligence algorithms.

Yes, Each client can choose whether to receive data as delivered by the original source or prefer it to be adjusted using standardization mechanisms and missing data filling techniques.

If a metric is received from multiple sources (E.g., Garmin And Apple Health), a priority criterion will be applied to select the most reliable one, preventing duplicates in the analysis.

Some of the data that has already been standardized includes:

If a source sends data less frequently, imputation methods can be applied to fill based on averages and predictive algorithms.

Clients interested in this solution should contact their Customer Success representative to request this feature. Please note that this feature comes with an additional cost beyond the client´s existing plan.

No, We have implemented optimizations to ensure that standardization does not slow down data processing, seamlessly integrating into existing pipelines.

When searching for a consistent period in granular data, there may be cases where no data source contains the value corresponding to the generated timestamp.

In these cases, the client has 4 options:

For more details, you can contact our support team.