> 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/connecting/getting-a-provider-developer-app-approved/managed-vs-own-credentials.md).

# Which providers need my own credentials?

The Integration credentials column in the supported integrations table shows whether Terra manages a provider's credentials or you need your own app.

**Check the "Integration credentials" column in the** [**supported integrations**](https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations) **table.** It shows whether Terra manages the provider's credentials or you need your own developer app.

* **Managed:** Terra's own app with the provider is used, so there are no keys for you to enter. Oura, Fitbit, Polar, Withings and Suunto are managed.
* **Required:** you register your own developer app with the provider and add its credentials in your dashboard. Garmin, WHOOP, Strava, Huawei and Dexcom are examples, and that provider's own approval process and user limits apply to your app. For Garmin, enter the client ID and client secret of your own OAuth 2.0 production app, as described in [Garmin](https://docs.tryterra.co/unified-api/garmin).
* **N/A:** for providers shown under Connections, there is nothing to configure. Apple Health needs no credentials. Intervals.icu and Lyfta use each end user's personal API key, which the user enters when they connect.

Samsung Health through the direct SDK is marked Required and needs a partnership request approved by Samsung, as described in [Samsung Health Data SDK process](https://developer.samsung.com/health/data/process.html).