# \_auth\_TAUTULLI

Tautulli authentication provider (server URL + API key).

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

### What this auth provider does

Stores the Tautulli URL and API key so CrossWatch can import Plex history.

### Auth flow

* `api_key`

### Writes to config

Namespace:

* `cfg[\"tautulli\"]`

Common fields:

* `server_url`
* `api_key`
* optional `user_id`

### Related docs

* UI setup: [Auth: Tautulli](/crosswatch/providers/authentication/auth-others/auth-tautulli.md)
* Adapter: [Adapter: TAUTULLI](/crosswatch/providers/synchronization/adapter-tautulli.md)
* Sync module: [TAUTULLI module](/blueprint-architecture/sync/_mod_tautulli.md)

### Gotchas

* This provider is read-only and history-only.
* The URL must be reachable from the container.
  {% endtab %}

{% tab title="Power users" %}

### Code map

* `providers/auth/_auth_TAUTULLI.py`

### Public surface

* class: `TautulliAuth`
* function: `html()`

### Capabilities

<details>

<summary>Capabilities (raw)</summary>

```json
{
  "watchlist": false,
  "ratings": false,
  "history": true
}
```

</details>

### Dependencies

* `cw_platform.config_base.save_config`
  {% endtab %}
  {% endtabs %}


---

# Agent Instructions: 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:

```
GET https://wiki.crosswatch.app/blueprint-architecture/auth/_auth_tautulli.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.