> 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/byo-credentials-generic-provider-key.md).

# How do I set up a bring-your-own-credential provider?

Some providers require you to obtain API credentials **directly from the provider** before the connection will work. The flow:

{% stepper %}
{% step %}
**Contact the provider's API team** to request access.
{% endstep %}

{% step %}
**Enter the credentials** in the provider's source settings on the [dashboard](https://github.com/tryterra/api-faqs/blob/main/dashboard/README.md). For gym-type providers, enter your portal name as the client ID and the API key as the client secret.
{% endstep %}

{% step %}
**Confirm the credentials are saved.** An empty source-settings entry causes connections to fail.
{% endstep %}
{% endstepper %}

For developer-portal providers, you register the app and bring your own client ID and secret. For provider athlete or user limits, use the provider's limit-increase process.

See [setting up data sources](https://docs.tryterra.co/health-and-fitness-api/integration-setup/setting-up-data-sources) for more on configuring a source.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/connecting/setting-up-provider-credentials-bring-your-own-keys/byo-credentials-generic-provider-key.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.