# Managing user health data 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 [**Receiving data events (automatic updates)**](/health-and-fitness-api/managing-user-health-data/receiving-data-updates.md) * 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. [**Requesting historical data**](/health-and-fitness-api/managing-user-health-data/requesting-historical-data.md) * 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 [**Writing data to user accounts (e.g. planned workouts)**](/health-and-fitness-api/managing-user-health-data/write-data.md) * 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tryterra.co/health-and-fitness-api/managing-user-health-data.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.