# Polar

Polar excels in the wearable tech space by offering devices tailored for serious athletes and fitness enthusiasts. Their sports watches and heart rate monitors provide detailed performance analysis, surpassing basic activity tracking. 

## Data availability

#### Manually Added Polar Data

Not all data manually entered into Polar Flow mobile and web apps is made available through their API. There is no visual indicator in the Polar interface to distinguish between API-available and unavailable manually entered data.

## Create your own oAuth-client for Polar

Follow these steps to create your dedicated Polar oAuth-client and integrate its credentials with our data source connection system seamlessly.

1. **Create a Polar Flow account**

If you don’t already have one, create a Polar Flow account at [flow.polar.com](https://flow.polar.com/). Use this same account to sign in to the [Polar Developer Dashboard](https://admin.polaraccesslink.com/).

2. **Create a Client**

Register a new client by selecting [Create a client](https://admin.polaraccesslink.com/#/clients/create) in the Polar Developer Dashboard.

Please fill in your company's details:

<figure><img src="/files/ex9qVVAXv9apSm7BnQU8" alt=""><figcaption><p>Illustrative Example: Contractual Information</p></figcaption></figure>

Ensure that the provided information is accurate, then click on "Next"

Please fill in your application's details:

* Set Authorization redirect URL: `https://${partnerName}.und-gesund.de/dataSourcesSwitch.html`&#x20;
* Set the data types (scopes) you wish to receive from your Polar users

<figure><img src="/files/2d2phTFiTOhM2YWhpjdE" alt=""><figcaption><p>Illustrative Example: Application Information</p></figcaption></figure>

Ensure that the provided information is accurate, then click on "Next" and create your Polar oAuth-client

&#x20;

3. **Share credentials with Thryve**

After you have created your App, you will be provided with your:

* ClientID
* ClientSecret

Please encrypt these credentials, along with the requested data types, using our [secret sharing service](https://secret.thryve.de/) and then [share](https://thryve.zendesk.com/hc/en-us/requests/new) the resulting link with our Customer Operations Team.

{% hint style="info" %}
Understanding the `${appName}` Variable

In this guide, you'll see the placeholder `${appName}`. Whenever you encounter it, replace it with your actual partner name, exactly as it's registered in our system.<br>

For example, if your partner name is `yourcompany`, then:

`https://${appName}.und-gesund.de/dataSourcesSwitch.html`&#x20;

should become:

`https://yourcompany.und-gesund.de/dataSourcesSwitch.html`&#x20;

If you're unsure what your `${appName}` is, please refer your web authentication username, it usually follows the format `${appName}-api`. Otherwise, feel free to [contact us](https://thryve.zendesk.com/hc/en-us/requests/new) and we’ll confirm it for you.
{% endhint %}


---

# Agent Instructions: 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.thryve.health/thryve-data-sources/polar.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.