Terra API Routes

Terra API Routes is a write-to-device product (pre-release): define a GPS route once with waypoints, and Terra API pushes it to your users' connected devices for on-device navigation. The route appears on the watch or bike computer after the user's next device sync, so your app never has to speak each provider's native route format.

Only Garmin, COROS, and Wahoo are supported. Feature coverage differs sharply between them (see the provider matrix below), so design routes for the lowest common denominator unless you know every user is on Garmin.

Account tools: CLI or MCP

Routes is pre-release, so it has no account commands and its endpoints are not in the API description the CLI bundles: terra admin-api list --data-api will not show them. terra data-api sends them anyway, because the server, not the CLI, validates the path:

terra data-api /routes -X POST --body-file route.json
terra data-api /pushedRoutes -q user_id=<uuid>

Add -i for the status line, --jq to filter the response; a DELETE asks for confirmation unless you pass --yes.

The account configuration around Routes does have commands. terra unified-api sources list --env <dev-id> says which of the devices below are enabled, and terra users list --env <dev-id> --provider GARMIN says whether a user is connected to push a course to.