> 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/anilist.md).

# AniList

{% tabs %}
{% tab title="End users" %}

<figure><img src="https://565675962-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F3rh5THg1PdhVsBt3GALo%2Fuploads%2FWJkUuJcWMFP559gaLY7m%2Fimage.png?alt=media&amp;token=fea8ea24-3f9b-4dbd-b07d-a942ec0772d4" alt=""><figcaption></figcaption></figure>

Connect AniList to synchronize supported anime activity with CrossWatch.

### What CrossWatch can sync

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

| Feature    | Read | Write | Notes                                                                                           |
| ---------- | ---- | ----- | ----------------------------------------------------------------------------------------------- |
| Watchlist  | Yes  | Yes   | Anime movies and series in Planning.                                                            |
| History    | Yes  | Yes   | Watched anime movies and episode counts; requires Anime ID Mapping. No separate rewatch events. |
| Ratings    | Yes  | Yes   | Anime movies and series.                                                                        |
| Progress   | No   | No    | Resume positions are unsupported; watched episode counts use History.                           |
| Playlists  | No   | No    | Unsupported.                                                                                    |
| Collection | No   | No    | Unsupported.                                                                                    |

**Live scrobbling:** Scrobble destination for completed anime movies and episodes only.

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

### Connect AniList

1. Create an AniList developer app:
   1. Open <https://anilist.co/settings/developer>
   2. Click **Create New Client**
   3. Set **Name**: `CrossWatch`
   4. Set **Redirect URL**: the callback shown by CrossWatch, for example: `http://<your-server-ip>:8787/callback/anilist`
2. Copy the **Client ID** and **Client Secret** into CrossWatch.
3. Click **Connect AniList**.
4. Approve access. Wait until you see:

```
AniList authorized. You can close this tab and return to the app.
```

{% hint style="warning" %}
If you later switch CrossWatch from **HTTP ↔ HTTPS** (or change host/port), update the AniList **Redirect URL** to match.

Guide: [HTTPS/TLS](https://wiki.crosswatch.app/crosswatch/advanced-and-api/https-and-tls.md).
{% endhint %}

### Troubleshooting

* If the auth tab doesn’t open, disable popup blockers for CrossWatch.
* If authorization fails, double-check the redirect URL matches exactly.
* AniList tokens expire after \~1 year. Reconnect yearly.
  {% endtab %}

{% tab title="Power users" %}

## Power users

### Config keys

Stored under:

* `anilist.*`

### Related docs

* Sync module: [AniList module](https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/anilist.md)
* Adapter: [Adapter: AniList](https://wiki.crosswatch.app/crosswatch/settings/synchronization/trackers/anilist.md)
  {% 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/anilist.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.
