New Long Term Support (LTS) version of ROOK SDKs,version 4.0.0. This version is designed to maximize the reliability, scalability, and maturity of Health Kit integrations such as Apple Health, Health Connect, and Samsung Health. This update transforms the SDK integration with your app, offering a more stable and predictable environment for developers and customers.
The version 4.0.0 It ensures that every integration with health data sources , more robust, and more predictable for all supported ecosystems:
- Frameworks móviles: React Native, Flutter y Capacitor.
- Nativo: iOS y Android (Health Connect y Samsung Health).
Security Update
This release outlines our strategic migration regarding the authentication schema between our backend services and SDKs. We are evolving our current model toward a stateless security architecture, specifically designed to enhance operational efficiency and streamline secret rotation.
Under this new framework, security and verification will be bolstered through mandatory signing of requests. Development teams will now be required to provide their Bundle ID/Package Name along with a secret word. These credentials must be configured directly within the ROOK Portal to ensure seamless and secure communication between services.
This transition represents a significant step forward in our commitment to providing a robust, scalable, and highly secure environment for our global partners.
Important:
Configure your secret word, meaning that this word will sign the requests between ROOK and SDK , you will need the Bundle ID (iOS) and Package Name (Android). If you don't have one of these, you will need to provide your internet domain.
Learn more about how to get this in this article
SDKs focused on stability and control
The update addresses the need to improve the synchronization and data retrieval experience of Apple Health Health Connect, and Samsung Health.
Improved visibility through Notification Webhooks
To transform the operation of the SDKs into a transparent flow, we have integrated Notification Webhook. This will allow us to notify clients of the following events:
- User created: Notification after successful registration of a new user through the SDK.
{
"client_uuid":"YOUR-CLIENT-UUUID",
"user_id":"EXAMPLE-USER",
"action":"user_created",
"level":"info",
"data_source":"apple" | "healthConnect" | "samsung",
"message":"A new user has been successfully created",
"action_datetime":"2025-07-02T19:23:14.393487",
"environment":"sandbox"
}
- Permission request: Alert when the SDK launches the permission request pop-up to the user.
{
"client_uuid":"YOUR-CLIENT-UUID",
"user_id":"EXAMPLE-USER",
"action":"permission_request_launched",
"level":"info",
"data_source":"apple" | "healthConnect" | "samsung",
"message":"SDK launched permission request pop-up",
"action_datetime":"2025-07-02T19:23:14.393487",
"environment":"sandbox"
}
- Background synchronization: Confirmation that the SDK has successfully started collecting data in the background.
{
"client_uuid":"YOUR-CLIENT-UUID",
"user_id":"EXAMPLE-USER",
"action":"background_sync_started",
"level":"info",
"data_source":"apple" | "healthConnect" | "samsung",
"message":"SDK successfully initiated background sync",
"action_datetime":"2025-07-02T19:23:14.393487",
"environment":"sandbox"
}
- Deleted user: Alert when a user is deleted from the SDK.
{
"client_uuid":"YOUR-CLIENT-UUID",
"user_id":"EXAMPLE-USER",
"action":"user_deleted",
"level":"info",
"data_source":"apple" | "healthConnect" | "samsung",
"message":"User has been successfully deleted",
"action_datetime":"2025-07-02T19:23:14.393487",
"environment":"sandbox"
}
Identification of pre-existing data
From the version 4.0.0, Health records will include a flag to identify historical data.
- Summaries and events prior to the SDK installation date will have the value true in the pre-existing data field.
- This allows companies to clearly differentiate between historical information and new data generated after integration with their application.
Mandatory update and notice of important changes
This version introduces significant architectural improvements to the ROOK SDK. Please note that this is a mandatory update containing major changes that will require modifications to your current integration. The SDK version change must be made by September 30, 2026.
FAQ
What is version 4.0.0 LTS?
This is a Long Term Support (LTS) release designed to maximize the reliability, scalability, and maturity of integrations with Health Kits. This update provides a more stable and predictable environment for developers.
Which ecosystems and frameworks does this update support?
Version 4.0.0 is compatible with the following environments:
- Frameworks móviles: React Native, Flutter y Capacitor.
- Nativo: iOS, Android (Health Connect) y Samsung Health.
Why is this update mandatory?
This version introduces significant architectural improvements. As it is a mandatory update, it contains important changes that require modifications to each client's current integration. The SDK version change must be made by September 30, 2026.
What improvements does it include for health data management?
The update improves the Apple Health and Health Connect data synchronization and retrieval experience, as well as expanding direct compatibility with Samsung Health.
How can historical data be distinguished from new data?
Starting with this version, logs include a flag to identify pre-existing data. Summaries and events prior to the SDK installation date will have the value "true" in the pre-existing data field. This allows you to differentiate historical information from new data generated after integration.
What specific events trigger the Notification Webhook?
The system will report the following events:
- User created: After successful registration of a new user through the SDK.
- Permission request: When the SDK launches the permission request pop-up to the user.
- Background synchronization: Confirmation that the SDK successfully started collecting data in the background.
- Deleted user: When a user is removed from the SDK.