• Unified API
  • Mobile SDK
  • Connection Widget
  • Streaming
  • Lab Reports API
  • Graph API
  • Health Scores
  • Health Rewards
  • Planned Workouts
  • Lab Testing
  • AI Interface
  • Enterprise
  • Insurance
  • Integrations
  • Research
  • Podcast
  • Blog
  • Reports
  • Events
  • Documentation
  • Community
  • Example apps
  • Wearable Data
  • About
  • Customers
  • Partners
  • Careers
  • Support
  • Pricing
Terra
Pricing
Become an integrationGet started
next ventures
pioneer fund
samsung next
y combinator
general catalyst

The world's best health apps run on Terra data

Get started
ProductsIntegrationsAI InterfaceAuthenticationMobile DevelopmentDocumentationGraphAPI
DocumentationAPISDKQuickstart
CommunityBlogResearchCommunityPodcastAuthorsGithub
CompanyAboutCareersCustomersBecome an IntegrationCookies PolicyGDPRPrivacy PolicyTerms of Purchase
© Terra API. 2026 — All rights reserved.

Cookie Preferences

Essential CookiesAlways On
Advertisement Cookies
Analytics Cookies

Crunch Time: Embrace the Cookie Monster Within!

We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.

Cookies Policy
All articles

In this article:

  • 01Disconnecting a user now revokes their access at the provider
  • 02Force a backfill when you need a user's history again
  • 03Catapult joins the source catalogue
  • 04Vantage: Order blood and DNA tests, and get the results as data
  • 05Also in December
All articles

Product Updates

December 2025 product update: revoking access properly, forced backfills, and Vantage early access

December 2025: disconnecting a user now revokes access at the provider, force backfill returns history on demand, Catapult joins the catalogue, and Vantage opens early access.


Alex Venetidis
Alex Venetidis

1 January 2026

Terra health data API product update for December 2025: new integrations, endpoints and developer features

TL;DR: When one of your users disconnects, Terra calls the provider's own revocation endpoint, so the grant is torn down at the source. That is the behaviour a privacy review expects and the behaviour a user assumes they are getting, and it is now true by default on every account. December also brought a force backfill option for pulling a user's history again on demand, Catapult as a new source, and early access to Vantage, the API for ordering blood and DNA tests and receiving the results as structured data.

Disconnecting a user now revokes their access at the provider

There is a meaningful difference between forgetting a token and revoking it. If your app stops using a token but never tells the provider, the grant still exists. It still shows up on the user's connected-apps page. It could, in principle, still be used. Users who go looking, and privacy teams who go looking on their behalf, notice this.

From December, when a user is disconnected through Terra, Terra calls the provider's own revocation endpoint where one exists, so the grant is actually torn down at the source.

This is the kind of detail that surfaces during a security questionnaire or a data protection impact assessment, which is to say under deadline and in front of someone else's legal team. Having the right answer already true, and being able to point at the revocation call that makes it true, is worth considerably more at that moment than a plan to implement it.

Get the latest Terra Research reports and insights every week as soon as they're published.

By continuing, I agree to the Privacy Policy and Terms of Service.

Force a backfill when you need a user's history again

Terra normally pulls a user's historical data once, when they first connect, and then keeps them up to date going forward. That is the right default, because a historical pull is expensive for everyone involved and the providers all impose rate limits that are shared across your whole user base.

Occasionally, though, you genuinely need the history again. You have added a new data type to your integration and want it filled in for existing users. You are migrating to a new database and want a clean load. You are onboarding a cohort you first imported before a schema change of your own. A force backfill option on the request re-runs the historical pull for that user, on your schedule and without a conversation with us.

Historical requests, and the difference between them and the event stream, are covered in requesting historical health data.

Catapult joins the source catalogue

Catapult is used widely in professional and collegiate team sport, where athletes wear a tracking unit during training and matches and the coaching staff work from the resulting load data. Adding it to Terra means a performance platform can read Catapult sessions through the same payload shape it already uses for consumer watches, which matters because most teams have both: the squad wears the club's units in training and their own watches everywhere else.

The full list of what Terra connects to is on the integrations page.

Vantage: Order blood and DNA tests, and get the results as data

Vantage opened for early access earlier this year and has now expanded to UK as well. Instead of reading data a person has already generated, Vantage lets you order a diagnostic test for them, track its fulfilment through to the lab, and receive the results in FHIR, which is the standard interchange format healthcare systems use for clinical data.

The reason this sits next to wearable data rather than in a separate company is that the two answer different halves of the same question. A wearable tells you what is happening day to day, at very high frequency and fairly low precision. A blood panel tells you what is happening at the level of underlying physiology, at very low frequency and much higher precision. Products that combine the two are noticeably better than products that have only one, and until now combining them meant a commercial relationship with a lab network and a great deal of paperwork.

The Vantage documentation, including the catalogue of available panels and the order lifecycle, is at the Vantage API docs. If you would rather start from a PDF you already have, Lab Reports turns an existing lab report into structured biomarker data.

Also in December

  • Withings: the sleep score reported by the device is now carried through in the sleep payload.
  • TrainingPeaks: completed sessions are now distinguished from scheduled ones, so a plan and its execution stay separable, and calorie figures come through on the activity.
  • Polar: data collection begins the moment a user authorises, so their first payloads land while they are still in your onboarding flow.
Previous
Next

Continue reading

  • Terra now delivers per-set strength training data

    Terra now delivers strength workouts set by set: reps, weight, effort and rest, normalized across nine integrations including watch-sensed Garmin sets.

    8 September 2026

  • Garmin's Connect Developer Program is paused: what it means if you're building on wearable data

    Garmin paused new Connect Developer Program applications while it updates the program. What the pause covers, why Garmin data matters, how to keep shipping.

    7 September 2026

  • Terra's Routes API: Get training routes on your user's watch

    Design an activity route once, and it lands on your users' watch ready to follow, with none of the usual file wrangling!

    6 September 2026