Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

ROOK (BYOK) — connector documentation

  • MCP endpoint: https://byok-rook.connectorbay.com/mcp
  • REST API: POST https://byok-rook.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-rook.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own ROOK ROOK client UUID, sent in the X-Upstream-Key header and the ROOK client secret key in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-rook.connectorbay.com/health · Tool schemas: https://byok-rook.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-rook · agent@connectorbay.com

What ROOK (BYOK) is for

ROOK (BYOK) lets an AI assistant read your own ROOK data through the ROOK API with a key you supply (ROOK client UUID). Read-only: 6 tools (list_authorized_data_sources, get_users_status, get_physical_summary, get_sleep_summary, get_body_summary, get_nutrition_summary). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.rook-connect.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ROOK. ROOK and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which wearables has ROOK user app-user-42 connected?"
  • "How many active users does my ROOK project have?"
  • "How active was ROOK user app-user-42 on 2026-10-02?"
  • "How did ROOK user app-user-42 sleep on 2026-10-02?"
  • "What did ROOK user app-user-42 weigh on 2026-10-02?"
  • "How many calories did ROOK user app-user-42 eat on 2026-10-02?"

What it does

  • list_authorized_data_sources: List the data sources (Garmin, Oura, Fitbit, Apple Health and others) one end user has authorized in ROOK, with an authorized flag for each.
  • get_users_status: List the users of your ROOK project with active flag, creation date and the data sources they authorized, as of a date up to six months back. Paged; the answer carries total counts and pagination.
  • get_physical_summary: Get one end user's physical summary for a day: seconds at each activity intensity, calories, steps, distance, floors, elevation gain and heart rate (average, minimum, maximum, resting, HRV). An empty answer means no data for that day.
  • get_sleep_summary: Get one end user's sleep summary for a day: start and end, total, light, REM and deep sleep seconds, time in bed, time to fall asleep, awake time, quality and efficiency ratings, heart rate, HRV and breathing rate. An empty answer means no data for that day.
  • get_body_summary: Get one end user's body measurements for a day: weight, height, BMI, waist, hip and chest circumference and body composition percentages. Only these measurements are returned. An empty answer means no data for that day.
  • get_nutrition_summary: Get one end user's food intake for a day from connected nutrition apps: calories, protein, carbohydrates, fat, fibre, sugar, sodium and total food in grams. An empty answer means no data for that day.

BYOK key

You bring your own ROOK ROOK client UUID (https://docs.tryrook.io/docs/portal-configuration/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.rook-connect.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Read-only. Answers are wearable data of the end users in the key owner's own ROOK project, not clinical records. Uses the production host (api.rook-connect.com); sandbox credentials need the sandbox host and do not work here.

Data sources

Live from the ROOK API (api.rook-connect.com) with a BYOK key; documentation: https://docs.tryrook.io/api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by ROOK. ROOK and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your ROOK account.

Built for: Worldwide. Languages: English.