Connect a user's wearable to Terra using the Terra Connect widget and receive standardized workout/activity payloads via webhook from any of its 500+ supported providers.
domain: docs.tryterra.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Sign up at dashboard.tryterra.co to get a dev-id and x-api-key.
Embed the Terra Connect widget so end users can link a wearable or app (e.g. Garmin, Oura, WHOOP, Strava) to your dev-id.
Configure a destination webhook endpoint to receive Terra's HTTP POST payloads when new data syncs.
Verify incoming payloads and map Terra's standardized data-model fields for the activity types needed.
Use the docs.tryterra.co reference (or its .md export) to confirm current field names per data type, since Terra reorganizes docs frequently.
Known gotchas
Terra's data delivery is event-based/webhook-push, not simple polling — architect for asynchronous arrival after a user's device syncs.
Terra is an aggregator, not the source of truth — data freshness and completeness depend on each underlying provider's own sync cadence.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?