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.

ROOK takes a step forward in the accuracy and accessibility of physical activity data with the launch of Steps Event in API Based Data Sources, a new feature that enables hourly step event extraction directly from the API Based Data Sources. Until now, this capability was only available through SDK integration, leading to inconsistencies in data collection for clients relying exclusively on the API Based Data Sources.

This new functionality implements an advanced polling mechanism that queries each data source every hour, ensuring real-time data updates. Additionally, the system is optimized to respect each provider’s API rate limits, ensuring smooth and efficient integration.

Below is a sample JSON payload delivered when receiving step event data through our Data Webhook:

This enhancement not only improves data accuracy but also prepares ROOK’s infrastructure to support a growing user base without compromising performance. The microservices-based architecture and use of scalable technologies ensure that Steps Event in API Based Data Sources remains a robust and future-ready solution.

Steps Event in API is a new feature that enables hourly step event extraction directly through the ROOK API, providing real-time access to users’ physical activity data.

Previously, step event data was only available via SDKs, leading to inconsistencies in data retrieval. With this update, the API now offers synchronized and precise information.

SDKs: ROOK already extracts step data every hour from SDKs integrated with devices such as Apple Health and Health Connect.

API: With this new feature, the API can now extract step data hourly, aligning with the information obtained from SDKs.

ROOK’s API uses a polling mechanism that queries each data source every hour while ensuring API rate limits from each provider are not exceeded.

If no step data is found in a query, the API will return the following structure with accumulated_steps_int set to 0:

To prevent duplicate records, the following rules apply:

ROOK currently supports integration with the following APIs:

Currently, the API only allows real-time step data extraction on an hourly basis. pre-existing data retrieval is not supported through this method, but users can access physical summaries for past data.

To enable this feature, clients must validate their access with ROOK. For more details on integration, technical documentation, or support, please contact the ROOK support team.

This mobile application is designed to simplify user data extraction, primarily to facilitate SDK integration, optimizing the process for both users and clients. The application offers an automated way to collect health data and send it to the appropriate clients, who can then use the collected data, ensuring a quick and seamless integration.

The ROOK Extraction App works by scanning QR codes or using universal links provided by ROOK to authenticate their session, where users can easily connect their health kits (SDKs) and data sources to the app. Once connected, the app securely sends the extracted data to ROOK, allowing clients to enhance their digital platforms with health data from their own users. This minimizes the need for direct user interaction while ensuring that all relevant data is transmitted and processed in real-time.

The ROOK Extraction App will be available on both the Google Play Store and Apple App Store. Users can also download the app by scanning a QR code or clicking a universal link provided by the client. During initial setup, users will be prompted to link their health data sources and start the extraction process with ease.

Learn more about ROOK Extraction App in our documentation.

ROOK Extraction App is a mobile application that acts as an intermediary between the user and the client to facilitate the integration, especially of SDKs, of ROOKConnect. It allows users' health data to be extracted and delivered to clients so that they can quickly and easily use it for the benefit of their users. This app also provides a simple health score to users who link their data sources as they receive their health summaries.

ROOK Extraction App is an add-on product to ROOKConnect and is available for select ROOK plans. For more information, please contact the ROOK team.

You will need to integrate the Binding endpoint to create access for your users. Visit our documentation for more details.

The application does not require prior activation. You only need to integrate the endpoint and make the query.

You will need to provide a URL in the Data Webhook through the ROOK Portal. The delivery of user data will then occur via the webhook, ensuring timely data delivery as it becomes available.

They can download it from the App Store or Play Store.

Using the Endpoint, you must generate a link or QR code to provide to the user for access. Each link and QR code is unique and must only be used by one user. You will need to request a separate link or QR code for each user.

We are working on a new feature in our API with the Data Source Endpoint Separation functionality. This enhancement allows applications to obtain data from each source individually, optimizing the efficiency, scalability, and security of the system.

Until now, developers accessed all data sources configured for a user through a single endpoint. With this update, each request can be directed to a specific source, such as Dexcom, Fitbit, Garmin, Oura, Polar, Whoop, or Withings, improving performance and reducing unnecessary data overhead.

This update gives developers more precise control over data applications, making it easier to integrate with applications that require wearable-specific information.

For the current authorizer endpoint:

Which will be answered as follows:

For more information, please see our API Reference.

This is an improvement to our API that allows requesting authorization data for a specific source (such as Fitbit, Garmin, or Oura) instead of retrieving information for all sources at once. This enhances system efficiency, security, and scalability.

Previously, developers received information from all sources in a single request, which could generate unnecessary data and slow down responses. With this improvement, only the needed source data is retrieved, optimizing performance and security.

It gives them greater control over data integration in their applications. Now, they can request specific information from each wearable or health platform, improving system efficiency.

The new endpoint format is:

For example, to retrieve authorization data from Fitbit, the request would be:

A successful request will return a JSON with the requested source’s information. Example response for Fitbit:

The supported data sources include:

Not immediately, but it is recommended to take advantage of the efficiency and security benefits. The previous version will remain available for a limited time.

No, authentication still works with secure tokens, but now each request will validate credentials more specifically for each data source.

The new approach allows handling multiple concurrent requests more efficiently, reducing server load and improving response times.

If an unrecognized data source is requested, the system will return an error indicating that the source is invalid.

You can check our API reference documentation for more details on how to integrate this new endpoint into your applications.

Users are looking for an automated way to monitor their calorie expenditure without manual intervention. Currently, calorie burn data comes from multiple sources and can be inconsistent or difficult to synchronize in real-time.

To provide users with an effective tool for tracking calories burned throughout the day, we are excited to announce the launch of the 'Calories Events' project in the iOS and Android SDKs. This system will enable automatic data synchronization, ensuring accessibility and proper processing at all times.

The 'Calories Events' system is designed to collect, process, and present detailed information about users' calorie expenditure. Its architecture consists of several key components within the iOS and Android SDKs.

For more information on how to use the calories event, please see our SDK repository.

The 'Calories Events' project is designed to provide users with an automated and efficient way to track calories burned throughout the day. The system ensures seamless background synchronization, accurate data retrieval using SDKs for iOS and Android.

The system consists of key components, which are extracted by iOS and Android SDKs, then the data is processed, and calorie data is presented to users.

The system gathers calorie burn data from platforms like Apple Health and Health Connect and processes it using the SDKs.

The duplication system ensures that redundant calorie events are detected and removed before storage, maintaining accurate records.

Developers need to integrate the iOS or Android SDKs, ensuring proper setup for:

It is currently available for Android, iOS, Capacitor, React Native and Flutter.

At ROOK we are working on a new endpoint that allows its clients to efficiently query the status of their users linked to various data sources.

With this development, clients will be able to access detailed information about the total number of users, their authorized data sources, and their activity status, eliminating the need to manually review each user.

Currently, clients who want to know the status of their users depend on manual processes carried out by the ROOK team, which consumes time and resources. With this new endpoint, they will be able to obtain this data in real time through an API query, specifying a date to receive the relevant information up to that point.

The User State Endpoint is now available for ROOK customers with API access. For integration details, see the API Reference.

The User Status Endpoint is an API feature that enables ROOK clients to query and retrieve data about their linked users, including total users, data sources, and their activity status.

Only authenticated ROOK clients with API access can use this endpoint.

Clients send a request to with the parameter. The response provides a summary of total users, active users, and their associated data sources.

Clients can request data in CSV format using the format=csv parameter in the API request.

Clients must provide BASIC AUTH (, ) in the request header to access the endpoint. Unauthorized requests will receive a 401 Unauthorized error.

Detailed API reference.

enables ROOK to extract prior health information from users, providing clients with immediate access to user data from multiple sources. This feature ensures that clients can access up to 7 days of pre-existing data from API-based sources and up to 29 days from SDK-based sources, allowing for faster initial analysis. By delivering data and calculating initial ROOKScores as soon as a user connects, this feature enhances the onboarding experience and provides actionable insights without the typical waiting period for new data to accumulate.

With this project, clients can now automatically retrieve up to 7 days of historical data via the API or 29 days via the SDK for more accurate user wellness analysis. Additionally, this feature simplifies the calculation of an initial ROOKScore, providing clients with valuable insights into user wellness from the moment of connection.

ROOKConnect integration is compatible with various data sources, including Android, Apple Health, Garmin, Fitbit, Health Connect, Polar, Oura, Whoop and Withings. Compliance with privacy and security regulations is also ensured.

*

We are pleased to announce the release of ROOKScore 2.0, our enhanced health score. This new version introduces advanced metrics and improved functionality, allowing customers to gain deeper insights and foster greater innovation with users' health data.

ROOKScore 2.0 is a redesign of our health score, aimed at making it more consistent, providing a clearer overview of key user health indicators. While ROOKScore 1.0 offers a solid foundation, it lacks the depth and robustness needed to address the diverse needs of health-focused applications. This new version is built around our three health pillars: Body Health, Physical Health, and Sleep Health, offering a more personalized scoring system based on multiple factors.

As mentioned, ROOKScore 2.0 allows configuration of the health score’s structure, meaning you can adjust the weight of each health metric or pillar, or deactivate them if they should not contribute to your ROOKScore. To configure your ROOKScore 2.0, log in to your ROOK Portal and go to the ROOKScore module. Keep in mind the following:

To access ROOKScore 2.0, please contact the ROOK team.

ROOKScore 2.0 is the enhanced version of our health scoring system. This version includes advanced metrics and improved functionality, offering a deeper and more accurate assessment of user health.

ROOKScore 2.0 incorporates additional health metrics like body mass index (BMI) and heart rate variability (HRV), as well as a new three-pillar structure: Body Health, Physical Health, and Sleep Health. It also allows metric customization and provides a more dynamic evaluation based on multiple days rather than daily snapshots.

ROOKScore 2.0 includes new metrics such as BMI, steps, calories burned, activity time, and sleep duration and quality, offering a more comprehensive view of physical, body, and sleep health.

The three pillars are:

Each of these pillars contributes to the final score and can be configured based on customer needs.

Yes, ROOKScore 2.0 allows customers to adjust the weight of each metric and pillar according to their priorities. This offers the flexibility to focus on the most relevant aspects of user health.

ROOKScore 1.0 will continue to function for some time. However, we recommend migrating to ROOKScore 2.0 to take advantage of its new features. We provide documentation and support to ensure a smooth transition.

To configure ROOKScore 2.0, log in to the ROOKScore module in your ROOK portal, where you can adjust the weight of the health pillars and metrics. Assign a percentage to each pillar (Body Health, Physical Health, and Sleep Health) and metric, ensuring that the total adds up to 100%.

If you do not want a pillar or metric to participate in the score, you can deactivate it or assign it a value of 0%, which will prevent it from contributing to the ROOKScore.

To integrate ROOKScore 2.0, contact the ROOK team for access and technical support.

We are excited to introduce our new feature, "Step Events." This enhancement allows users to obtain hourly step metrics, significantly improving the experience and insights available to our customers.

Previously, the only way to access step data through ROOK was via the Physical Summary, which provides a daily summary of steps after the day ends, or through Physical Events during specific activities. However, many customers have expressed the need to obtain step information throughout the day at various times. In response, we developed "Step Events," a solution that allows frequent and manual step updates, getting as close to real-time as possible.

Step data accumulates from 00:00 to the current time of day and is transmitted via an optimized JSON to ensure quick visualization of the metrics. Here is an example of the JSON used:

“Step Events" is a new feature launched by ROOK that allows users to obtain hourly step metrics. This functionality significantly enhances the user experience and provides more detailed insights for our customers.

No, this functionality is integrated with the ROOK SDKs.

"Step Events" addresses the need for more frequent step information updates, allowing manual and frequent data updates, getting as close to real-time as possible.

The SDKs extract and update step data as frequently as possible in the background, every hour.

Available for iOS, Android, React Native, Flutter, and Capacitor SDKs.

On iOS devices, data is extracted from Apple Health; on Android devices, data is extracted from Health Connect and the Android operating system data.

Step data accumulates from 00:00 to the current time of day and is transmitted via an optimized JSON to ensure quick visualization of the metrics.

At ROOK, we continually strive to enhance our API's ability to deliver meaningful and actionable health data. In line with this commitment, we are pleased to announce the release of ROOKScore 1.5, a significant update to our readiness score.

Many users observed that the readiness score consistently displayed a rating of 100% in various scenarios. After thorough analysis, we identified that the issue lay in the intervals defined for generic users, i.e., those whose age or gender were not specified.

Initially, the readiness score intervals were as follows:

The breadth of these intervals, averaging 82 points, contrasted markedly with the narrower average range of 35 points for users with known age and gender. This disparity caused the readiness score to be disproportionately high for generic users, often resulting in a perfect score of 100%.

To address this, we conducted a review and adjustment of the intervals for generic users. This process incorporated data on average population ages from recognized sources such as the United States Census Bureau, Eurostat, and the Instituto Nacional de Estadística y Geografía (INEGI). Based on this research, we have established the following updated intervals:

These refined ranges better reflect global population trends and are expected to provide a more accurate readiness score for generic users.

With ROOKScore 1.5, we are confident that our readiness score will now offer more precise insights, allowing our users to maximize the potential of our API. We remain committed to continuous improvement and appreciate ongoing feedback to ensure our tools meet the highest standards of accuracy and utility.

ROOKScore 1.5 is an update to our ROOKScore, designed to offer a more precise measurement through the readiness score, adjusting for global demographic trends for users who do not have demographic data.

It was identified that the undefined demographic intervals for generic users were too broad, resulting in disproportionately high and irrational readiness scores. This update adjusts those intervals through demographic data standardization to improve accuracy.

The new intervals were defined using data on average population ages from recognized sources such as the United States Census Bureau, Eurostat, and INEGI. The following age ranges were established for users without demographic data:

We expect the readiness scores to be more accurate and better reflect demographic reality, providing more useful insights.