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

# FlickList

{% tabs %}
{% tab title="End users" %}
FlickList tracks movies, shows, and episodes. CW syncs watchlists, ratings, history, progress, and playlists. It can also scrobble to FlickList.

FlickList does not support Collection sync.

<figure><img src="/files/FRE2fLHw7Yx1jalH7C8O" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Use **Device Code** for new connections. You do not need an API key.
{% endhint %}

### Connect FlickList

1. Open **Settings → Authentication → FlickList**.
2. Leave **Device Code** selected.
3. Click **Connect**.
4. CrossWatch shows a link code and opens `https://flicklist.tv/link`.
5. Sign in to FlickList and approve the code.
6. Return to CrossWatch. It shows **Connected with Device Code**.

### Troubleshooting

* If the FlickList page does not open, allow popups. You can also open `https://flicklist.tv/link` manually.
* If the code expires, start the Device Code flow again.
* If authentication continues to fail, disconnect FlickList and reconnect.
  {% endtab %}

{% tab title="Power users" %}

## Power users

CrossWatch supports **Device Code** and **API Key** authentication. Device Code is the recommended default.

### Device Code

CrossWatch uses its built-in FlickList client ID. No client configuration is required.

The flow opens `https://flicklist.tv/link`. CrossWatch stores the returned credentials. It associates the connection with the API user.

Set a custom client ID with `CROSSWATCH_FLICKLIST_CLIENT_ID` or `flicklist.client_id`.

### API Key

1. Open **Settings → Authentication → FlickList**.
2. Select **API Key**.
3. Paste your key and save.
4. CrossWatch validates the key against the FlickList user endpoint.

Minimal configuration:

```json
{
  "flicklist": {
    "auth_method": "api_key",
    "api_key": "YOUR_API_KEY"
  }
}
```

### Config keys

* `flicklist.auth_method`
* `flicklist.api_key`
* `flicklist.access_token`
* `flicklist.expires_at`
* `flicklist.username`
* `flicklist.user_id`
* `flicklist.client_id`

Additional profiles are stored under `flicklist.instances`.

Set provider limits with `flicklist.rate_limit.get_per_sec` and `flicklist.rate_limit.post_per_sec`. Both default to `0.2` requests per second.
{% 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/flicklist.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.