> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/routes-api/provider-compatibility.md).

# Provider compatibility

What Garmin, COROS, Wahoo and Hammerhead support for routes.

Not every provider supports every route feature. This page shows what works where.

### Operations

|                        | Garmin | COROS | Wahoo | Hammerhead |
| ---------------------- | ------ | ----- | ----- | ---------- |
| **Push**               | ✓      | ✓     | ✓     | ✓          |
| **Update**             | ✓      | ✓\*   | ✓     | ✓          |
| **Delete from device** | ✓      | —†    | ✓     | ✓          |

\*COROS has no update API. Terra uploads the route again under the same route ID, and `provider_route_id` stays the same.

†COROS has no delete API. Deleting removes the route from Terra only, and it stays on the user's device. The API still returns success.

### Sports

Every provider accepts every sport. COROS groups them into running (`running`, `trail_running`, `hiking`) and cycling (everything else), so its devices may not tell a road ride from a gravel ride.

### Features

|                        | Garmin | COROS | Wahoo | Hammerhead |
| ---------------------- | ------ | ----- | ----- | ---------- |
| Elevation per waypoint | ✓‡     | ✓     | ✓     | ✓          |
| Elevation gain/loss    | ✓      | ✓     | ✓     | ✓          |
| Speed target           | ✓      | —     | —     | —          |
| Course points (POIs)   | ✓      | —     | —     | —          |
| Description            | ✓      | —     | —     | —          |

‡Garmin needs elevation on all waypoints or none. If only some waypoints have it, Terra drops all of it and Garmin fills elevation from its own model.

A provider that doesn't support a feature ignores it, and the rest of the route still arrives.

### Provider details

#### Garmin

**Limitations:**

* Doesn't show the `left`, `right`, `straight`, `left_fork` and `right_fork` course point types.
* Elevation must be on all waypoints or none.

**Behavior:**

* If the user deleted the course from their device, an update recreates it under a new `provider_route_id`.

***

#### COROS

**Limitations:**

* No update or delete API (see [Operations](#operations)).
* No course points, speed target or description.

***

#### Wahoo

**Limitations:**

* No course points, speed target or description.

**Behavior:**

* If the user deleted the route from their device, an update recreates it under a new `provider_route_id`.

***

#### Hammerhead

Routes go to the user's Karoo.

**Limitations:**

* No course points, speed target or description.
* The user must have allowed route access. Users who connected before route support was added need to reconnect; until they do, a push returns `403 Forbidden`.

**Behavior:**

* Hammerhead only updates a route in place when its path changes. If an update keeps the same waypoint positions, for example a new name or new elevations, Terra replaces the route on the device with a new one, under a new `provider_route_id`. A repeat push of an unchanged route does the same.
* If the user deleted the route from their device, an update recreates it under a new `provider_route_id`.

### Best practices

* Design for Garmin first: it supports the most features.
* Don't rely on course points unless your users are on Garmin.
* Put elevation on every waypoint or none.
