Auth: TMDb
TMDb can be used in CrossWatch in two different ways.
Metadata (recommended): improves matching across providers. Setup guide: Meta: TMDb.
TMDb (Sync): connects your TMDb account so CrossWatch can read/write TMDb data.
This page covers TMDb (Sync).
What it supports
Watchlist
Ratings
If you only want better matching, you want Metadata → TMDb, not TMDb (Sync).

Connect TMDb (Sync)
Disconnect
Open Settings → TMDb (Sync).
Click Disconnect.
Troubleshooting
Auth tab didn’t open: disable popup blockers for CrossWatch.
Stuck on “Pending approval”: approve in the TMDb tab, then click Verify.
“TMDb did not return a session id”: restart the flow with Connect and approve again.
Verify keeps failing: the server must reach
https://api.themoviedb.org/3.Key issues: the key must be a valid TMDb v3 API key.
Security notes
Treat your TMDb API key and session as secrets.
They are stored in CrossWatch config on disk.
Config keys used
TMDb (Sync) stores values under:
tmdb_sync.api_keytmdb_sync.session_id
Metadata stores a separate key under:
tmdb.api_key
API endpoints (manual flow)
Start / Verify / Finish / Disconnect
CrossWatch exposes a small API used by the UI.
These are useful for debugging or headless setup.
Start (opens the approval URL)
POST /api/tmdb_sync/connect/start
Open the returned auth_url and approve.
Verify (auto-finish after approval)
GET /api/tmdb_sync/verify
Finish (optional explicit completion)
POST /api/tmdb_sync/connect/finish
Disconnect
POST /api/tmdb_sync/disconnect
Last updated
Was this helpful?