Terra Docs
Dashboard
  • Docs
  • API Reference
  • Changelog
  • Getting Started
    • What is Terra API?
    • Account setup and API keys
    • Core concepts
  • Health & Fitness API
    • Overview
    • Quickstart
    • Integration setup
      • Understanding sources and destinations
      • Setting up data sources
      • Setting up data destinations
        • Webhooks
        • SQL database (Postgres, MySQL)
        • Supabase
        • Cloud storage (S3, GCP)
        • Queuing services (SQS, Kafka)
      • Customising data types
      • Dedicated data source API keys
      • Understanding Terra environments
    • User authentication
      • Authentication flow
      • Implementation (Terra widget)
      • Implementation (Custom UI)
      • Handling authentication events
      • Customising authentication redirects
    • Managing user health data
      • Receiving health data updates (events)
      • Requesting historical health data (REST API requests)
      • Writing data
    • Mobile-only sources
      • iOS (Swift)
      • Android (Kotlin)
      • React Native
      • Flutter
    • Troubleshooting
    • Pricing
  • User Engagement
    • Health Scores
  • Streaming API
    • Overview
    • Wearable -> Your app
      • iOS (Swift)
      • Android
    • Your app -> Terra
      • iOS (Swift)
      • Android
    • Terra -> Your backend
  • Teams API
  • Biomarkers API - Upcoming
Powered by GitBook
On this page
  • Retrieving user data
  • Writing data

Was this helpful?

  1. Health & Fitness API

Managing user health data

Access user health and fitness information from Terra and, where supported, write data back to connected services.

PreviousCustomising authentication redirectsNextReceiving health data updates (events)

Last updated 17 days ago

Was this helpful?

Once your integrations are setup and you're successfully authenticating users, the next step is to interact with their health and fitness data. This section covers the methods for accessing the data Terra collects and the procedures for sending data back to supported providers.


Retrieving user data

  • Learn how Terra automatically pushes new health and fitness data as events to your configured destination whenever it becomes available from a user's connected source (e.g. via Webhooks). This is the primary method for receiving ongoing user data.

  • Understand how to make API requests to fetch batches of past data for a user. This is useful for initial data backfills, analytics, or ad-hoc data retrieval.


Writing data

  • Understand how to use Terra to send data, such as planned workouts, from your application back to a user's account on their fitness platform.

Receiving data events (automatic updates)
Requesting historical data
Writing data to user accounts (e.g. planned workouts)