> 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/help-center/help-topics/data-api-sdk/api-endpoints-errors-and-migrations/unsupported-data-type-per-provider.md).

# Why do I get a 404 connection does not support data type error?

A 404 invalid data type saying this connection does not support the requested data type means the connected provider does not offer that data type.

A `404` **`invalid data type`** with the error **`this connection does not support the requested data type`** means the connected provider does not offer that data type. For example, Strava only supports `activity`, not `daily`, so request `/v2/activity` for Strava users.

**Check each provider's supported data types before requesting**, in the [supported integrations reference](https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations).

**Other responses to a `to_webhook=false` request mean different things:**

* **`200` with an empty `data` array:** the request worked and there is no data for that user in that window or, just after a user connects, history is still being fetched.
* **`400`** **`data type is not enabled, enable on the dashboard`:** the data type is switched off for your environment. Enable it in the dashboard.
* **`424`** **`request failed due to a provider permission issue`:** the provider refused the request for this user. If a required permission wasn't granted or access was revoked, the user needs to reconnect and accept every permission.
* **`424` with `provider server issue`, `provider rate limit issue` or `failed to retrieve data, please contact support`:** Terra couldn't get the data from the provider. If it affects every user on a provider, contact support with a user ID and the request time.

With `to_webhook=true` (the default) the response only confirms the request was accepted, and the data arrives at your destination.

Use only documented endpoints. Historical data is:

```
GET https://api.tryterra.co/v2/{dataType}
```

where `dataType` is `daily`, `activity`, `sleep`, `body`, `nutrition` or `menstruation`, with `user_id`, `start_date` and `end_date` as query params, and `dev-id` plus `x-api-key` headers. A `404` without that error usually means an invented or misspelled path. See [requesting historical data](https://docs.tryterra.co/unified-api/managing-user-health-data/requesting-historical-data).