How does ROOK’s User Profile work?

User Profile transforms the data already synced to ROOK into a structured profile that gives applications a broader view of a user's health and wellness.

Instead of working with individual metrics from different wearable sources, ROOK organizes the available data into five key areas:

Each profile can include aggregated metrics, scores, health levels, trends, data coverage, and personalized insights.

The profile is generated on demand and delivered asynchronously through the webhook configured for your ROOK integration.

The process follows four main steps:
​

Wearable data synced to ROOK

↓

Your application requests a profile

↓

ROOK processes the available health data

↓

ROOK sends the profile to your webhook
​

ROOK primarily analyzes the user's last seven days of data. Some Recovery calculations may use up to 14 days of sleep data.

The profile is built from data that has already been synced and stored in ROOK. It does not connect directly to the user's wearable during profile generation.

The profile contains five sub-profiles:

Depending on the available data, each sub-profile can include:

The profile also includes:

Scores are grouped into five levels:

These scores provide context about the available data. They are not medical diagnoses.

The overall score combines the five areas using these weights:

Sub-profiles without usable data are not treated as negative results.

Missing data does not mean that a user's profile result is poor.

For example, a low step count can contribute to a lower activity score, but having no step data does not produce the same result.
​

When a metric is unavailable, ROOK uses the other available metrics when possible and reflects the reduced data availability through coverage or confidence.

If there is not enough information to calculate a sub-profile, its values may be returned as null:

{ "score_int": null, "level_string": null, "trend_string": null }

A null value should not be interpreted as zero or as a negative result.

If there is not enough information to generate any sub-profile, ROOK does not generate or send an empty profile.

User Profile is available through the ROOK API and follows an asynchronous workflow.

At a high level:

Request profile → ROOK processes the data → Profile delivered via Data Webhook

Before requesting a profile, make sure that:

The profile is not updated automatically when new wearable data becomes available. If new data is synchronized after a profile has been generated, you must request a new profile to have ROOK process the updated data.

If you are interested in trying User Profile feature, contact Customer Success team to enable the feature for your organization.
​

For complete integration details, including API requests, authentication, webhook configuration, payloads, retries, rate limits, and error handling, see the User Profile technical documentation