Terra vs Thryve: Which Wearable Data API for Your App?

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#

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, Thryve API pricing and the Terra integration guide.

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.