> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/connections/trackers/wetrakr.md).

# WeTrakr

Connect WeTrakr to sync watch activity, ratings, and playback progress.

## WeTrakr

{% tabs %}
{% tab title="End users" %}
Connect WeTrakr to sync your watchlist, watched history, ratings, and playback progress with CrossWatch. It can also receive scrobbles from your configured players.

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FafE4wFMnCfZcDMtrqf83%2Fimage.png?alt=media&amp;token=99a35fd4-7214-4798-89d1-a152078b5b4e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You do not need an API key, client secret, or developer account. Approve CrossWatch in WeTrakr, then copy the authorization code back into CrossWatch.
{% endhint %}

#### Connect WeTrakr

1. Open **Settings → Connections** and select **WeTrakr**.
2. Select the provider profile you want to connect.
3. Click **Connect WeTrakr**.
4. In the browser tab that opens, sign in to WeTrakr and approve CrossWatch.
5. Copy the authorization code displayed by WeTrakr.
6. Return to CrossWatch and paste it into **Authorization code**.
7. Click **Complete connection**.
8. Wait until CrossWatch shows **Connected as** your account name.

Keep the connection dialog open and stay on the same provider profile while completing these steps. The login session expires after 10 minutes.

#### Account status

After connecting, CrossWatch displays your account name and **Free** or **VIP** plan. The provider status tooltip also shows your remaining daily API calls and reset time when WeTrakr supplies that information.

Connecting an account does not start synchronization automatically. Configure your sync pairs or scrobble routes separately. Rewatch syncing is optional in the pair settings and does not require WeTrakr VIP.

#### Troubleshooting

* If no browser tab opens, click **Open WeTrakr approval page** or allow popups for CrossWatch.
* If the code is invalid or the login session expires, click **Connect WeTrakr** again and complete the new approval flow.
* If CrossWatch asks you to reconnect, repeat the connection steps for the affected profile.
* If you reach an API quota, wait for its reset before retrying. Check the provider status tooltip for the remaining allowance when available.
  {% endtab %}

{% tab title="Power users" %}

### Power users

#### Authentication

CrossWatch uses **Authorization Code + PKCE (S256)** with the out-of-band redirect URI `urn:ietf:wg:oauth:2.0:oob`. The browser displays a code for the user to paste into CrossWatch; no public callback URL is required.

CrossWatch includes its public client ID and does not require a client secret. WeTrakr's media-center Device Code flow is not used for this connection.

Access and refresh tokens are stored automatically for the selected provider profile. CrossWatch refreshes access tokens automatically; reconnect if authorization expires or is revoked.

#### Config keys

The `wetrakr` provider configuration includes:

* `auth_method`: `pkce`
* `access_token`, `refresh_token`, `token_type`, `expires_at`: managed by CrossWatch
* `username`, `user_id`, `plan`: account details obtained during authentication
* `reauth_required`: whether the profile needs to reconnect

Use the connection UI to manage credentials. Additional provider profiles keep their own authentication state.

#### Related docs

* [WeTrakr API documentation](https://api.wetrakr.com/)
* Provider rate limiting
  {% endtab %}
  {% endtabs %}


---

# 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, and the optional `goal` query parameter:

```
GET https://wiki.crosswatch.app/crosswatch/settings/connections/trackers/wetrakr.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.