> 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/faq/help-topics/connecting/setting-up-provider-credentials-bring-your-own-keys/inbody-no-dedicated-credentials-needed.md).

# What credentials do I need for InBody?

The InBody integration works with **end-user accounts directly**: users authenticate with the same username and password they use in the InBody app. The standard InBody integration uses end-user accounts directly, so most setups need **no separate developer credentials** and you can start using it right away.

A dedicated OAuth2 partnership with InBody is optional and only needed for specific direct-API use cases. Reach out to support if you are unsure which applies to you.

{% hint style="info" %}
An older Teams-API path used a `facility_id` and API key issued by InBody for a purchased device, but the standard integration no longer requires this.
{% endhint %}