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

# TMDb Metadata

Configure TMDb metadata to improve matching and stabilize IDs across providers.

{% 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%2FruRWsMkTvzIi1lhcG0YU%2Fimage.png?alt=media&amp;token=06bba7b6-c7bf-45ba-aa7d-d23e766fdb86" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
CrossWatch uses TMDb for many features.

TMDb is strongly recommended if you want posters, backdrops, richer metadata, and more reliable matching.
{% endhint %}

### Setup

{% stepper %}
{% step %}

### Create a TMDb API key

1. Create a TMDb account.
2. Request an API key here: <https://www.themoviedb.org/settings/api>
   {% endstep %}

{% step %}

### Add the key to CW

1. Open **Settings → Connections**.
2. Paste your API key.
3. Click **Save**.
   {% endstep %}
   {% endstepper %}

{% hint style="info" %}
This key is used for matching only.

If you want TMDb watchlist/ratings syncing, connect **TMDb Sync** instead: [TMDb](/crosswatch/settings/connections/trackers/tmdb.md).
{% endhint %}

### Settings

<details>

<summary>Language / Locale</summary>

Controls the language used for titles, overviews, and other localized fields.

PublicMetaDB TMDb enrichment uses this setting too.

Pick a locale code from the list below.

</details>

<details>

<summary>Cache TTL (hours)</summary>

Controls how long CW caches posters and other TMDb payloads.

PublicMetaDB TMDb enrichment uses this cache too.

Default is `720` hours.

Higher TTL = fewer API calls.\
Lower TTL = fresher metadata.

</details>

### Supported locales

These locale codes control the language/region used for TMDb lookups.
{% endtab %}

{% tab title="Power users" %}

### Config keys

Metadata:

* `tmdb.api_key`
* `metadata.locale`
* `metadata.ttl_hours`

TMDb (Sync):

* `tmdb_sync.api_key`
* `tmdb_sync.session_id`

### Related docs

* Sync setup: [TMDb](/crosswatch/settings/connections/trackers/tmdb.md)
* Adapter: [Adapter: TMDb](/crosswatch/settings/synchronization/trackers/tmdb.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/metadata/tmdb-metadata.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.