Setting up data destinations

Overview

Terra’s Health & Fitness API is event-based; meaning it pushes all user health payloads via events directly to your data destination and removes the need to request data via the API.

Therefore, setting up data destinations is a core step in your integration process.

Terra API provides many options for data destinations such as webhooks, SQL databases, Supabase, and buckets.

In this section, you'll learn how to set up your preferred destination in your Terra Dashboard.

---

Set up Data Destination

• Head to your Terra Dashboard > Connections page.

• Click on "Add New", and select from 10 data destinations: Webhook, Database, Bucket and other.

• Add the necessary details and click on "Apply".

You don't have a data destination yet?

No worries! If you are just starting off building your product and want to test how Terra works, you can use https://webhook.site to set up a temporary destination for Webhooks.

For further information about each destination, please see Destinations in the Reference page.

---

Destination-specific steps

Terra API supports various data destinations, some require additional steps to setup correctly. Click each for further information and detailed setup instructions:

Webhooks

• The most basic destination. Terra makes a POST request to your specified URL with new data events.

SQL database (Postgres, MySQL)

• Store structured data directly into your PostgreSQL or MySQL databases. Terra can manage table creation and data insertion, providing download links for full payloads.

Supabase

• Leverage the combined power of Postgres and S3-compatible storage. Terra integrates seamlessly to manage both your database entries and raw data payloads within Supabase.

Cloud Storage (AWS S3, GCP GCS, Azure Blob)

• Dump raw data payloads directly into your preferred cloud storage bucket (AWS S3, Google Cloud Storage, or Azure Blob). Suitable for archival, batch processing, or data lake strategies.

Queuing services (AWS SQS, Kafka)

• Integrate with managed message queues like AWS SQS or Kafka for resilient, scalable, and asynchronous data ingestion into your existing event-driven architectures.