> ## Documentation Index
> Fetch the complete documentation index at: https://auth0.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Fitbit

> Connect your AI agent to a user's Fitbit account to track fitness data and set new fitness goals.

Connect your AI agent to a user's Fitbit account to track fitness data, log activities or food intake, and set new fitness goals.

## Connect Fitbit to Auth0

**1. Fitbit setup**

1. Visit the [Fitbit Developer account](https://dev.fitbit.com/) page and sign up.
2. Create a new application in the Fitbit Developer Console.
3. Complete the application details form.
4. Select the **OAuth 2.0 Application Type**.
5. Configure OAuth redirect URL:

   * **Redirect URL**: `https://YOUR_AUTH0_DOMAIN/login/callback`

   You can find the **Auth0 domain** in the [Auth0 Dashboard](https://manage.auth0.com/).

   You can find this under **Applications > \[Your Application] > Settings > Basic Information > Domain**.

   If you are using the [custom domains](/docs/customize/custom-domains.md) feature, your Auth0 domain is the custom domain. You can find this under **Branding > Custom Domains**.
6. **Default Access Type**: Select **Read-Only** or **Read and Write**.
7. Select **Save**.
8. After creation you'll be shown the Client ID and Client Secret.
9. Copy the Client ID and Client Secret.

To learn more about setting up Fitbit, read the [Developer guide for Fitbit documentation](https://dev.fitbit.com/build/reference/web-api/oauth2/).

**2. Auth0 setup**

<ol>
  <li>In the [Auth0 Dashboard](https://manage.auth0.com), go to
  **Authentication > Social**.</li>
  <li>Select **Create Connection**, then choose **Fitbit**.</li>
  <li>Select **Continue**.</li>

  <li>
    In **General**:

    <ol type="A">
      <li>Enter the **Client ID** and **Client Secret** from
      your Fitbit OAuth app.</li>

      <li>
        Under **Attributes**, select the scope(s) required for your
        application. These determine what permissions your application can
        request from Fitbit, whether for authentication (such as
        accessing basic profile details) or for API access (such as
        connecting to the provider's APIs).

        For a Dropbox and Google social
        connection, you must select **Offline Access** in the Auth0 Dashboard, enabling
        the client application to obtain an Auth0 refresh token.
      </li>
    </ol>
  </li>

  <li>In **Purpose**, toggle on **Connected Accounts for Token Vault**. This lets the
  connection retrieve and securely store access tokens for external
  APIs. Learn more in
  [Connected Accounts for Token Vault](/docs/secure/call-apis-on-users-behalf/token-vault/connected-accounts-for-token-vault.md).</li>
  <li>Select **Create**.</li>

  <li>
    After creation, you are redirected to the **Applications** page.
    Select the application(s) to enable this connection for.

    In a new Auth0 tenant, you can select the **Default App**.
  </li>

  <li>Once you have created your Fitbit social connection, [test your connection](/docs/authenticate/identity-providers/test-connections.md) to ensure the setup is working correctly before using it in your application.</li>
</ol>

This guide walks you through setting up the **Fitbit** connection in Auth0.
For an end-to-end example that shows how to set up your app to call third-party APIs on the user's behalf
using a connection like this, read the
[Call third-party APIs on user's behalf quickstart](/ai/docs/get-started/call-third-party-apis-on-users-behalf.md).

## Token Vault configuration example

To configure the Token Vault for your Fitbit connection, you can use the following code snippet in your application:

**JavaScript**

**Python**

## Next steps

* To learn how to configure applications to access Token Vault, read [Configure Token Vault](/docs/secure/call-apis-on-users-behalf/token-vault/configure-token-vault.md).
* If your application uses [Organizations](/docs/manage-users/organizations.md), authenticate the user with the target organization before initiating the Connected Accounts flow. Connected accounts remain linked to the individual user profile.
* To learn how to get an access token to make a tool call, complete the [Call third-party APIs on user's behalf Quickstart](/ai/docs/get-started/call-third-party-apis-on-users-behalf.md).