Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

PublicMetaDB

Connect PublicMetaDB to synchronize supported activity with CrossWatch.

PublicMetaDB support is experimental.

Prefer a one-way flow into PublicMetaDB.

Start with your media server as the source and PublicMetaDB as the target.

TMDb Metadata is required for proper enrichment.

PublicMetaDB uses an API key.

CrossWatch can also enrich missing titles and release years for PublicMetaDB items in watchlist, history, ratings, and progress.

That enrichment needs TMDb Metadata and a TMDb API key.

It runs only when the PublicMetaDB item already has a TMDb ID and is missing the field.

Connect PublicMetaDB

  1. Open Settings → Connections.

  2. Open PublicMetaDB.

  3. In PublicMetaDB, create an API key in Settings → API.

  4. Paste the key into API Key.

  5. Click Connect.

  6. If needed, click Verify once.

API keys usually start with pm-.

Profiles

PublicMetaDB supports multiple profiles.

Use Profile to switch between Default and extra profiles.

Click New to add a profile.

Click Delete to remove a non-default profile.

Guide: Profiles

Troubleshooting

  • “Connected” only means CrossWatch saved an API key.

  • Verify checks the key against PublicMetaDB.

  • Missing titles or years usually mean TMDb metadata is not configured, the item has no TMDb ID, or the field already came from PublicMetaDB.

  • If verify fails, rotate the key in PublicMetaDB and reconnect.

Power users

Config keys

Stored under:

  • publicmetadb.api_key

  • publicmetadb.instances.<profile>.api_key

Common shared settings:

  • publicmetadb.base_url

  • publicmetadb.watchlist_name

  • publicmetadb.watchlist_list_id

  • publicmetadb.ratings_label

  • publicmetadb.rate_limit.get_per_sec

  • publicmetadb.rate_limit.post_per_sec

Pair-level watchlist overrides are stored under:

  • providers.publicmetadb.watchlist_name

Auth behavior

CrossWatch stores the API key and marks the provider as connected.

A deeper health check validates the key against PublicMetaDB.

CrossWatch sends the key as a bearer token.

Related docs

PreviousMDBListNextPunchPlay

Last updated

Was this helpful?