Terra vs ROOK: Which Aggregator API for Your App?
Last verified October 17, 2026 · 5 min read
Sources checked (16) · October 17, 2026
- tryrook.io/rookconnect/medical-device-api/ — Rook Medical Device API
- tryrook.io/rookconnect/lab-data-api/ — Rook Lab Data API
- tryterra.co/ — Terra coverage, data types, destinations, labs, compliance and pricing FAQ
- docs.tryterra.co/unified-api/integration-setup/setting-up-data-sources — Terra data source count and providers with special setup
- docs.tryrook.io/data-sources/ — Rook data sources and own developer accounts
- tryrook.io/wearable-api-sdk/integrations/ — Rook source catalogue
- docs.tryterra.co/unified-api/getting-started — Terra mobile-only sources, signed webhooks, rate limits
- docs.tryterra.co/unified-api/integration-setup/setting-up-data-destinations/webhooks — Terra webhook signing, retries and timeout
- tryrook.io/rookconnect/wearable-api/ — Rook wearable API, SDKs and delivery
- tryterra.co/products/lab-testing — Terra lab testing geography and collection methods
- tryterra.co/pricing — Terra plans, credits, add-ons and Enterprise terms
- tryrook.io/pricing/ — Rook plans, add-ons and contract terms
- docs.tryrook.io/ — Rook health score
- docs.tryterra.co/reference/health-and-fitness-api/supported-integrations — Terra integration credential requirements
- docs.tryterra.co/unified-api/pricing — Terra credit tiers
- tryrook.io/rookconnect/ehr-emr-api/ — Rook EHR/EMR API
Covered here:TerraWHOOPStravaGarminHealth Connect
Both are single-integration aggregators, so this is not a "which has an API" question; it is which billing unit, delivery model and extras fit your app. Everything below is from Terra's and ROOK's own pages as we read them on October 17, 2026. An earlier version of this page described both vendors' pricing as unpublished, called ROOK wearables-only, and repeated a Latin America positioning and a third-party per-user price estimate; the current pages publish prices, show ROOK selling medical-device and lab-report APIs, and say nothing about Latin America, so those claims are gone.
At a glance#
| Dimension | Terra | ROOK |
|---|---|---|
| Coverage claim | "500+ providers" on its site; its docs say the Unified API "supports over 150+ Data Sources" | "400+ wearables and health data sources" in its docs; "72 data sources and more than 500 devices" on its integrations page |
| How sources connect | Cloud APIs from your backend; a mobile SDK for Apple Health, Samsung Health and Health Connect | Direct API integrations for cloud providers; SDKs for Apple Health and Health Connect; 59 of its 72 listed sources are Indirect, reached through those phone stores |
| Delivery | Signed webhooks, or straight into SQL databases, Supabase, cloud storage, SQS and Kafka, MongoDB or Firestore | Webhooks or API queries |
| Beyond wearables | Lab test ordering (US and UK), DNA tests, a lab-report parsing API, streaming, planned workouts | Medical Device API, Lab Data API (report parsing), EHR/EMR API on a waitlist, a 0 to 100 health score |
| Entry price | $399 a month billed annually ($499 monthly), 100,000 credits | Core at $399 a month for up to 750 active users |
| How the bill grows | 200 credits per connected data source per month; extra credits from $0.005 | Core+ $999 (5,000 users), Business $1,999 (15,000), Enterprise custom |
| Contract | 30-day money-back guarantee on Quick Start | Standard term 12 months, cancel with 30 days' notice |
| Your own provider accounts | Its docs name WHOOP, Dexcom, Huawei, Strava and Virtuagym; its integrations table also marks Garmin and Samsung as Required | Dexcom, Samsung Health, Strava and WHOOP |
Where Terra wins#
Delivery options and lab ordering. Terra pushes every payload to a destination you choose, and its webhooks are signed: "Every webhook sent by Terra includes an HMAC-based signature header". Beyond webhooks it can write straight into "SQL databases (Postgres and MySQL), Supabase, cloud storage (S3, GCS and Azure Blob), queueing services (SQS and Kafka), MongoDB and Firestore". It also orders lab tests ("Nationwide US, plus the UK") and DNA tests, which we did not find on ROOK's pages; ROOK parses lab reports your users already have.
Breadth claims. Terra's catalog claim is larger, and its FAQ lists Garmin, Fitbit, Apple Watch, Oura Ring, WHOOP, Polar, Samsung Health, Withings, Suunto and Wahoo among sources. Both vendors count differently, so check your users' devices in each live list.
The trade-off. Terra's unit is the connected data source, not the person: "An active authentication is one connected data source for one end user, and costs 200 credits per month". A user with a watch and a ring costs twice. See the Terra integration guide for the build.
Where ROOK wins#
A bill you can read off one table. ROOK prices by plan and active users, and its pricing page lists each ceiling: Core $399 a month for up to 750 active users, Core+ $999 for up to 5,000, Business $1,999 for up to 15,000. At 1,000 users that is $999 on Core+, against about $899 on Terra by our arithmetic; at 5,000 users ROOK's Core+ is still $999 while Terra is about $4,899, assuming one source per person and annual billing. Past a plan's ceiling, ROOK says "billing adjusts based on usage" without a published rate.
Medical devices and lab reports. ROOK's Medical Device API delivers "glucose, blood pressure, oxygen saturation, temperature and ECG readings in one format, with the device that recorded each one", and its Lab Data API "turns PDF and image lab reports into structured biomarkers with LOINC codes and FHIR R4 output". Its EHR/EMR API, a waitlist item on the pricing page, delivers wearable data to clinical systems as FHIR R4.
A score and an app. ROOK Score gives "a simple score, ranging from 0 to 100", and the ROOK App "lets end users connect supported sources without embedding the SDKs", useful for programs without their own mobile app.
The trade-off. The standard contract term is 12 months, and add-ons cost extra on Core: Business and Enterprise include every product and add-on, while Core+ includes three.
What we could not verify#
- ROOK webhook signing. The ROOK pages we read describe webhook delivery but not a signature scheme; check the docs before you rely on one.
- Overage rates. Neither ROOK's usage rate past a plan's ceiling nor Terra's Enterprise terms are published.
- What "500 devices" means. ROOK's own pages give two counts, 400+ sources in the docs and 72 sources with 500+ devices on the integrations page.
Which should you pick?#
- Many users, mostly one device each, and a budget you want flat: lean ROOK; its active-user ceilings are easier to plan against than per-source credits at a few thousand users.
- Users who connect several sources each, or data pushed straight into your warehouse: lean Terra for its destinations; model the per-source credits first.
- Lab tests ordered for your users: Terra, which orders them in the US and the UK; ROOK parses reports users upload.
- Blood pressure cuffs, CGMs and ECG with the device recorded: lean ROOK's Medical Device API.
- Programs without a mobile app: ROOK App covers the phone stores for you.
For the rest of the field, see health-data aggregator APIs and aggregator pricing.
Bottom line#
Terra and ROOK both collapse dozens of wearable integrations into one normalized API. Terra's edge is delivery options and lab ordering; ROOK's is an active-user price sheet that stays flat longer, plus medical-device and lab-report APIs. Re-read both live pricing pages before you commit, because the numbers above are from October 17, 2026.
Frequently asked questions
- Do Terra and ROOK both give one integration for many devices?
- Yes. Both are single-integration aggregators that normalize data from many providers such as Garmin, Fitbit, Oura and WHOOP, plus Apple Health and Health Connect through mobile SDKs. As of October 17, 2026, Terra's site claims 500+ providers and ROOK's docs claim 400+ wearables and health data sources, while ROOK's integrations page lists 72 sources, so check your users' devices against each live list.
- How do their normalization models differ?
- Terra returns one schema for every source and pushes it to a destination you configure, from webhooks to SQL databases and queues. ROOK classifies sources into direct API integrations for cloud providers and SDK-based integrations for phone stores, delivers through webhooks or API queries, and adds a 0 to 100 health score. Both normalize into their own data models, so mapping to your schema is still your work.
- What are Terra and ROOK pricing models?
- Both are published as of October 17, 2026. Terra starts at $399 a month billed annually or $499 monthly, includes 100,000 credits, and charges 200 credits a month per connected data source plus credits for events past a free allowance. ROOK prices by plan and active users: Core $399 a month up to 750 active users, Core+ $999 up to 5,000, Business $1,999 up to 15,000, and custom Enterprise, on a standard 12-month contract.
- Which providers need my own developer account with Terra or ROOK?
- As of October 17, 2026, ROOK names Dexcom, Samsung Health, Strava and WHOOP and says setting them up can take several weeks. Terra's docs name WHOOP, Dexcom, Huawei, Strava and Virtuagym as needing special processes, and its integrations table also marks Garmin and Samsung as Required, though its homepage says Garmin data flows through Terra's own partner integration. Ask both vendors about your exact provider list.
- Which should I pick for a mobile app versus a backend service?
- Both ship mobile SDKs for Apple Health and Health Connect, so either works for a mobile app; ROOK also offers a ready-made ROOK App for programs without their own. For a backend-first product that wants data pushed into its own database, queue or cloud storage, Terra's destinations do more of the plumbing. Price the two at your expected user count before choosing.
Keep reading
Elsewhere on the site
Pages that share this one’s concepts and sources, from other sections.
Next steps
Was this page useful?
Independent comparison, last reviewed October 17, 2026. Pricing, rate limits, and feature availability change often — confirm current details in each provider’s official documentation before you commit. Product and company names are trademarks of their respective owners; AIFitnessAPI is not affiliated with, endorsed by, or sponsored by any product listed here.
← All comparisons · by AIFitnessAPI