> 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/synchronization/others/tautulli.md).

# Tautulli

Tautulli adapter notes for importing Plex watch history into CW.

Tautulli adapter is a **read-only history importer**. It pulls old Plex plays from an existing Tautulli database and normalizes them.

{% hint style="warning" %}
Tautulli is not a tracker and not a media server. Don’t use it to “sync” back into Plex/Trakt/SIMKL/etc.
{% endhint %}

{% hint style="info" %}
Connect Tautulli first. Use: [Tautulli (Authentication provider)](https://wiki.crosswatch.app/crosswatch/settings/connections/others/tautulli.md).
{% endhint %}

### What CrossWatch can sync

| Feature    | Read | Write | Notes                                                                                |
| ---------- | ---- | ----- | ------------------------------------------------------------------------------------ |
| Watchlist  | No   | No    | Unsupported.                                                                         |
| History    | Yes  | No    | Read-only Plex play history, including retained plays for unavailable library items. |
| Ratings    | No   | No    | Unsupported.                                                                         |
| Progress   | No   | No    | Unsupported.                                                                         |
| Playlists  | No   | No    | Unsupported.                                                                         |
| Collection | No   | No    | Unsupported.                                                                         |

**Read** brings data into CrossWatch; **Write** sends changes to this provider. Enable only features supported by both sides.

Connect the provider first: [Tautulli setup](https://wiki.crosswatch.app/crosswatch/settings/connections/others/tautulli.md).

### How indexing works

1. Pull pages from `get_history` until the end or a safety stop.
2. Keep only `media_type` in `{movie, episode}`.
3. Extract IDs from GUIDs + Plex/Tautulli keys (`rating_key`, `grandparent_rating_key`).
4. If IDs are incomplete, call `get_metadata(rating_key)` to enrich external IDs.
5. Emit normalized items keyed by external IDs where possible.

If Tautulli reports that metadata is unavailable for a history item, CrossWatch keeps the available history details and continues importing the remaining records. The item may have only a Plex ID, so another provider may not be able to match it. Authentication failures, connection failures, and other API errors still stop the read.

{% hint style="info" %}
History is indexed as a de-duplicated snapshot. Newest entry wins per canonical key.
{% endhint %}

### Output shape

<details>

<summary>Movie example</summary>

```json
{
  "type": "movie",
  "ids": {
    "imdb": "tt123",
    "tmdb": "456",
    "tvdb": "0",
    "plex": "12345",
    "guid": "plex://movie/..."
  },
  "title": "…",
  "year": 2024,
  "watched_at": "2025-12-30T23:54:11Z"
}
```

</details>

<details>

<summary>Episode example</summary>

```json
{
  "type": "episode",
  "ids": {
    "imdb": "ttSHOW",
    "tmdb": "157741",
    "tvdb": "397424",
    "plex": "40759",
    "guid": "plex://show/..."
  },
  "title": "Episode title",
  "year": 2025,
  "season": 2,
  "episode": 4,
  "watched_at": "2025-12-30T23:54:11Z",
  "series_title": "Show title (when available)",
  "show_ids": {
    "imdb": "ttSHOW",
    "tmdb": "157741",
    "tvdb": "397424",
    "plex": "40759",
    "guid": "plex://show/..."
  }
}
```

</details>

### Workflows (recommended)

{% stepper %}
{% step %}

### Import into CW (recommended)

Run a pair: **Tautulli → CW** with **History** enabled.

Then use **CW** as the source to seed Trakt/SIMKL/etc.

Related: [Adapter: CW](https://wiki.crosswatch.app/crosswatch/settings/synchronization/others/cw.md).
{% endstep %}

{% step %}

### Import into Editor dataset

Use this if you want to clean history before syncing it anywhere:

* fix wrong matches
* remove junk plays
* merge duplicates
* correct titles/years
  {% endstep %}
  {% endstepper %}

### Endpoints used (for debugging)

<details>

<summary>API calls</summary>

* History pages: `GET /api/v2?cmd=get_history`
* Metadata enrichment (optional): `GET /api/v2?cmd=get_metadata&rating_key=...`

</details>


---

# 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/synchronization/others/tautulli.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.
