> 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, playback progress, playlists, and your **My Library** collection 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%2FxtKjY4p21eWqov8TxvNl%2Fimage.png?alt=media&amp;token=e9b81328-bbd0-43d7-a690-8c4ede744f09" 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 %}

### What CrossWatch can sync

**Read** brings data into CrossWatch; **Write** sends changes to this provider.

| Feature    | Read | Write | Notes                                                                                  |
| ---------- | ---- | ----- | -------------------------------------------------------------------------------------- |
| Watchlist  | Yes  | Yes   | Movies and shows.                                                                      |
| History    | Yes  | Yes   | Movies and episodes; episode-zero records can be read but not written.                 |
| Ratings    | Yes  | Yes   | Movies, shows, seasons and episodes; episode-zero writes are unsupported.              |
| Progress   | Yes  | Yes   | Resume positions for movies and episodes; episode-zero writes are unsupported.         |
| Playlists  | Yes  | Yes   | Your own lists are writable; followed and liked lists are read-only.                   |
| Collection | Yes  | Yes   | My Library: movies and episodes, with media info and movie copies. One-way pairs only. |

**Live scrobbling:** Scrobble destination; cannot be a Watcher source.

See the [synchronization guide](https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/wetrakr.md) for matching rules and feature restrictions.

#### 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.

For My Library, configure a one-way **Collection** pair. Movies and episodes are supported, with movie copies and optional private details. See [WeTrakr collection sync](https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/wetrakr.md#collection-behavior).

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.

#### Playlists

WeTrakr appears in the **Playlists** provider list after you connect it.

Your own WeTrakr lists are writable. CrossWatch can add, remove, and reorder their items. They can be sources or destinations, including destinations in a pair playlist sync.

Followed and liked lists are read-only. Use them as sources only.

Add any public WeTrakr list as a source with its link:

```
https://wetrakr.com/lists/{id}
```

See [Playlists](https://wiki.crosswatch.app/crosswatch/main-dashboard/navigation/playlists.md) to create and run a playlist sync.

#### 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
