Terra API Planned Workouts

Push structured workouts directly to your users' fitness devices. Define a workout template once, and the Terra API syncs it to whatever device the user has connected: Garmin, COROS, Wahoo, Suunto, TrainingPeaks, Huawei, Zepp, Hevy, or Apple. This is a write-to-device product, the inverse of the read-focused Terra API Health & Fitness data flow.

Pre-release. This product is pre-release. Endpoints, fields, and provider behavior may change before general availability. Facts here are drawn from the Terra API docs; verify against docs.tryterra.co/planned-workouts-api before shipping.

Account tools: CLI or MCP

The whole create-then-plan flow can be driven by hand before you write the code that sends it:

terra data-api /workouts -X POST --body-file workout.json            # returns workout_id
terra data-api /workouts/<workout_id>/plan -X POST -q user_id=<uuid> -d planned_date=2026-09-08
terra data-api /plannedWorkouts -q user_id=<uuid>
terra workouts metadata list --env <dev-id>

The plan call is the one worth running by hand: it returns the planned workout id and any coercion warnings, which is how you find out that a target or an interval was rewritten to fit the device before a user sees it. Read what an endpoint takes with terra admin-api list --data-api /workouts --format json. These calls create and schedule real workouts on a connected device, so run them against a test user.