--- title: "Terra vs Thryve: Which Wearable Data API for Your App?" canonical: "https://aifitnessapi.com/compare/terra-vs-thryve" cluster: "Comparisons" primary_query: "terra vs thryve" last_reviewed: "2026-10-17" description: "Terra vs Thryve as of October 2026: credits per connected source vs per-user euro plans, a BAA on every plan vs Enterprise, German hosting and webhooks." publisher: "AIFitnessAPI — independent, not sponsored" cite_as: "\"Terra vs Thryve: Which Wearable Data API for Your App?\", AIFitnessAPI, https://aifitnessapi.com/compare/terra-vs-thryve" --- # Terra vs Thryve: Which Wearable Data API for Your App? > Terra and Thryve both connect wearables and phone health stores through one API, so the choice comes down to billing, compliance and plumbing. As of October 17, 2026, Terra starts at $399 a month billed annually with 100,000 credits, charges 200 credits a month per connected data source, lists its BAA on Enterprise, and can deliver to databases, cloud storage and queues as well as webhooks. Thryve's Start Up plan starts at 499 euros a month for 500 end users with 0.50 euros per extra user, includes a BAA on all plans and hosts all data in Germany, but stores data for only 2 weeks on Start Up and embeds its connect widget in an iframe. - Canonical: https://aifitnessapi.com/compare/terra-vs-thryve - Last reviewed: 2026-10-17 - Publisher: AIFitnessAPI (https://aifitnessapi.com) — independent, not sponsored - Cite as: "Terra vs Thryve: Which Wearable Data API for Your App?", AIFitnessAPI, https://aifitnessapi.com/compare/terra-vs-thryve --- Terra and Thryve both turn many wearables and phone health stores into one normalized API, and both publish prices. They differ on the billing unit, where the BAA sits, where the data lives and how the connect flow and webhooks work. Everything below is from Terra's and Thryve's own pages as we read them on October 17, 2026. ## At a glance | Dimension | Terra | Thryve | |---|---|---| | Coverage claim | "500+ providers" on its site; its docs say the Unified API "supports over 150+ Data Sources" | "500+ Wearables & Health Data Sources" on its site; the data-sources table in its docs lists 24 sources, two of them marked EOL (our count) | | Phone health stores | A mobile SDK for Apple Health, Samsung Health and Health Connect | A native SDK for Apple Health, Samsung Health and Health Connect | | Entry price | $399 a month billed annually, or $499 monthly, with 100,000 credits | Start Up from 499 euros a month with 500 end users | | Billing unit | 200 credits a month per connected data source, plus events past a free allowance | End users: 0.50 euros per user past the plan's included number | | Trying it | 30-day money-back guarantee | 14-day free trial with 25 end users | | BAA | Listed on Enterprise | Included on all plans | | Where data lives | Enterprise lists a "Dedicated instance to localised area" | "All data processed and stored by Thryve is hosted in Germany" | | Connect flow | Hosted widget session from your backend; no WebView or iframe | Connection Widget embedded in an iframe | | Webhooks | Signed with HMAC; up to 10 retries over about 8 hours; 8-second timeout | zstd-compressed; optional HMAC secret; up to 3 retries; respond within 2 seconds | | Other destinations | SQL databases, Supabase, cloud storage, SQS and Kafka, MongoDB and Firestore | None named; without webhooks you call its API | | Beyond wearables | Blood and DNA test ordering (US and UK), a lab-report API | Analytics and algorithms as value-added services | ## Where Terra wins **Delivery options.** Terra delivers "to webhooks, SQL databases (Postgres and MySQL), Supabase, cloud storage (S3, GCS and Azure Blob), queueing services (SQS and Kafka), MongoDB and Firestore", and "Every webhook sent by Terra includes an HMAC-based signature header". Its retry budget is larger: it "retries the delivery up to 10 times with exponential backoff", and "The cumulative window across all retries is ~8 hours". Thryve retries "up to 3 times", and "Recurring failed deliveries within a certain timeframe will lead to the automatic disabling of webhooks." **Lab ordering.** Terra can "Order blood and DNA tests for your users through Terra API", in the US and the UK. We did not find test ordering on the Thryve pages we read. **The trade-off.** Terra's unit is the connected data source: "An active authentication is one connected data source for one end user, and costs 200 credits per month", so a user with a watch and a ring costs twice. By our arithmetic the 100,000 included credits cover 500 connected sources before events past the free allowance. Its BAA sits on Enterprise. ## Where Thryve wins **The BAA on every plan.** Thryve's certifications page says "BAA agreements included on all plans — no enterprise upgrade required." For a HIPAA product that is the biggest difference on the two price sheets. **German hosting and two ISO certificates.** "All data processed and stored by Thryve is hosted in Germany", and its homepage claims compliance with "GDPR, HIPAA, ISO 9001, 27001 and other international regulations". Terra states that it is "HIPAA compliant, GDPR compliant, and SOC 2 Type II certified" and offers a localised dedicated instance on Enterprise. **Per-user plans with a startup tier.** Start Up starts at 499 euros a month for 500 users, and Scale Up, "Special plan for startups with growth-stage needs (less than 10 years of founding)", starts at 1,000 euros a month for up to 5,000 users. By our arithmetic, 5,000 one-source users cost about $4,899 a month on Terra at annual billing, against 2,749 euros on Thryve's Start Up or 1,000 euros on Scale Up if you qualify. We do not convert currencies; compare them at the rate you pay. **The trade-off.** Storage is short, 2 weeks on Start Up and 1 month on Scale Up, so keep your own history. The plan cards list custom auth credentials only on Scale Up and Enterprise, while Thryve's docs say that "When no shared oAuth-client is available, you must bring your own oAuth-client"; WHOOP, Dexcom and Google Health have none. ## How the connect flow differs Terra's widget is a hosted page: you "call POST https://access.tryterra.co/api/widget/session with your dev-id and x-api-key headers" from your backend, send the user to the URL, and its docs say "Do not use WebView or iFrame for the authentication flow." Thryve's is the opposite: "The Connection Widget must be embedded in your app using an iframe component", because "Opening the URL in a new tab or window will prevent the widget from properly redirecting users back to your web app." You first "create a Thryve user", then call its widget endpoint with two Basic Auth headers. If your app already opens provider logins in the system browser, Terra's flow fits it as is; Thryve's needs a page that can host the iframe. ## Your own provider credentials - **Terra** names "WHOOP Dexcom Huawei Strava Virtuagym" as providers that "require special processes", and its integrations table marks Garmin and Samsung as Required, though its homepage says Garmin data "flows through Terra today" through its long-standing partner integration. - **Thryve** marks WHOOP, Dexcom, Google Health and FreeStyle Libre (LibreView) without a shared OAuth client, while Garmin and Oura use Thryve's. Its table also marks Fitbit "Deprecating on Oct 29 2026". ## What we could not verify - **Thryve's per-user rate.** The Start Up card says "Additional users billed at €0.50 each" in its description and "€0.50 per additional user" in its feature list (as we read it on October 22, 2026), and neither names a billing period. - **Thryve's webhook signature format.** The docs say an HMAC secret can be configured, but the pages we read do not describe the header or algorithm. - **Fitbit on Thryve after October 29.** The docs mark the deprecation without saying how existing connections carry over. ## Which should you pick? - **A HIPAA product that needs a BAA from the first plan:** lean Thryve, which includes it on all plans; on Terra it is an Enterprise line. - **Data that should stay in Germany or the EU by default:** Thryve hosts in Germany; ask Terra about its localised dedicated instance on Enterprise. - **Data pushed straight into your warehouse, queue or cloud storage:** lean Terra. - **Lab or DNA tests ordered for your users:** Terra. - **Users who connect several sources each:** Thryve's plans count end users, while Terra counts each connected source; confirm how Thryve counts a user with several devices. For the rest of the field, see [health-data aggregator APIs](/fitness-apis/health-data-aggregator-apis), [Thryve API pricing](/pricing/thryve-api-pricing) and the [Terra integration guide](/integrate/terra-api). ## Bottom line Terra is the broader delivery and diagnostics platform, priced in dollars per connected source. Thryve is the compliance-first choice, priced in euros per end user, with the BAA on every plan and data hosted in Germany, at the cost of short storage windows and an iframe-based connect flow. Re-read both live pricing pages before you commit; these figures are from October 17, 2026. ## Sources - [tryterra.co/](https://tryterra.co/) — Terra coverage, data types, destinations, labs, compliance and pricing FAQ (checked 2026-10-17) - [docs.tryterra.co/unified-api/integration-setup/setting-up-data-sources](https://docs.tryterra.co/unified-api/integration-setup/setting-up-data-sources) — Terra data source count and providers with special setup (checked 2026-10-17) - [www.thryve.health/](https://www.thryve.health/) — Thryve coverage and hosting (checked 2026-10-17) - [docs.thryve.health/thryve-data-sources/overview](https://docs.thryve.health/thryve-data-sources/overview) — Thryve data sources and OAuth clients (checked 2026-10-17) - [docs.tryterra.co/unified-api/getting-started](https://docs.tryterra.co/unified-api/getting-started) — Terra mobile-only sources, signed webhooks, rate limits (checked 2026-10-17) - [tryterra.co/pricing](https://tryterra.co/pricing) — Terra plans, credits, add-ons and Enterprise terms (checked 2026-10-17) - [www.thryve.health/pricing](https://www.thryve.health/pricing) — Thryve plans, storage and hosting (checked 2026-10-17) - [www.thryve.health/certifications-compliance](https://www.thryve.health/certifications-compliance) — Thryve certifications and BAA (checked 2026-10-17) - [docs.tryterra.co/unified-api/user-authentication/implementation-terra-widget](https://docs.tryterra.co/unified-api/user-authentication/implementation-terra-widget) — Terra widget session endpoint and legacy deprecation (checked 2026-10-17) - [docs.thryve.health/connect-data-sources](https://docs.thryve.health/connect-data-sources) — Thryve connection widget (checked 2026-10-17) - [docs.tryterra.co/unified-api/integration-setup/setting-up-data-destinations/webhooks](https://docs.tryterra.co/unified-api/integration-setup/setting-up-data-destinations/webhooks) — Terra webhook signing, retries and timeout (checked 2026-10-17) - [docs.thryve.health/receive-updates-via-webhooks/data-push](https://docs.thryve.health/receive-updates-via-webhooks/data-push) — Thryve webhooks (checked 2026-10-17) - [tryterra.co/products/lab-testing](https://tryterra.co/products/lab-testing) — Terra lab testing geography and collection methods (checked 2026-10-17) - [docs.tryterra.co/unified-api/pricing](https://docs.tryterra.co/unified-api/pricing) — Terra credit tiers (checked 2026-10-17) - [docs.tryterra.co/reference/health-and-fitness-api/supported-integrations](https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations) — Terra integration credential requirements (checked 2026-10-17) ## FAQ ### Is Terra or Thryve cheaper? It depends on your user count and how many sources each user connects. As of October 17, 2026, Terra starts at $399 a month billed annually and charges 200 credits per connected data source per month, while Thryve's Start Up starts at 499 euros a month for 500 end users plus 0.50 euros per extra user. By our arithmetic, 5,000 one-source users cost about $4,899 a month on Terra, against 2,749 euros on Thryve's Start Up or 1,000 euros on its startup-only Scale Up plan. [Permalink](https://aifitnessapi.com/compare/terra-vs-thryve#faq-1) ### Do Terra and Thryve sign a BAA? Both offer one, on different plans. As of October 17, 2026, Terra's pricing page lists a signed BAA on its Enterprise plan, and Thryve's certifications page says BAA agreements are included on all plans with no enterprise upgrade required. Whether you need a BAA depends on your role under HIPAA. [Permalink](https://aifitnessapi.com/compare/terra-vs-thryve#faq-2) ### Where do Terra and Thryve host health data? Thryve says all data it processes and stores is hosted in Germany. Terra's Enterprise plan lists a dedicated instance in a localised area; the Terra pages we read on October 17, 2026 do not name a default hosting region, so ask Terra where your data would live. [Permalink](https://aifitnessapi.com/compare/terra-vs-thryve#faq-3) ### Can I embed the Terra or Thryve connect widget in an iframe? Only Thryve's. Thryve's docs say its Connection Widget must be embedded in an iframe, because opening it in a new tab breaks the redirect back to your app. Terra's docs say not to use a WebView or iframe for its authentication flow, and to open the hosted widget URL from a session your backend creates. [Permalink](https://aifitnessapi.com/compare/terra-vs-thryve#faq-4) ### Which providers need my own developer credentials with Terra or Thryve? As of October 17, 2026, 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. Thryve's data-sources table shows no shared OAuth client for WHOOP, Dexcom, Google Health or FreeStyle Libre, so you bring your own; Garmin and Oura use Thryve's shared client. Check your exact provider list with each vendor. [Permalink](https://aifitnessapi.com/compare/terra-vs-thryve#faq-5)