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

# Floppy

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

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

{% hint style="warning" %}
Floppy is experimental. Floppy API changes can affect the connection or supported features.
{% endhint %}

### Connect Floppy

Floppy connects to CW with its server URL and an API token.

#### Get an API token

1. Open Floppy.
2. Go to **Settings** → **Integrations**.
3. Create or copy an API token.

#### Connect Floppy

1. Open CW.
2. Go to **Settings** → **Connections** → **Authentication** → **Floppy**.
3. Enter the Floppy server URL. For example:

   ```
   http://<floppy-server>:8000
   ```
4. Enter the API token from Floppy.
5. Enable **Verify SSL** when Floppy uses HTTPS with a trusted certificate.
6. Click **Connect Floppy**.

CW validates the server URL and API token through the Floppy API. Its status then changes to **Connected**.

Create additional profiles to connect multiple Floppy servers or users.

### Supported synchronization

#### Watchlist

Movies and shows are supported. CW uses the configured Floppy list name.

The default list name is **Watchlist**. CW creates the list when needed.

#### Ratings

Movies and shows are supported. Ratings use a scale from 0 to 10.

#### History

Movies and individual episodes are supported. Show-level and season-level history are not supported.

#### Progress

Movies and individual episodes are supported. Show-level and season-level progress are not supported.

All supported Floppy synchronization requires TMDb identifiers.

### Troubleshooting

* If the API token is invalid, create a new token under **Floppy Settings** → **Integrations**.
* If CW cannot reach Floppy, confirm its URL is accessible from the CW host or container.
* When both apps use Docker, do not use `localhost` unless they share a container. Use the Floppy container name, host address, or another reachable address.
* If SSL validation fails, verify the certificate and **Verify SSL** setting.
* If CW reports an unexpected response, confirm Floppy is supported and exposes `/api/v1`.
* Items without a TMDb identifier cannot synchronize. CW reports them as unresolved.
* If Floppy returns `429 Too Many Requests`, reduce the Floppy provider throttling values.
  {% endtab %}

{% tab title="Power users" %}

### Limitations

Floppy support is experimental.

Playlists are not supported.

CW does not define validated stable volume limits for Floppy.

Floppy reads are paginated in batches of up to 200 items. CW applies an internal safety limit of 1,000 pages.

This is a CW safety limit. It is not a confirmed Floppy capacity limit.

The default provider throttling allows 20 GET requests and 20 POST 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/floppy.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.