keyAuthentication

Connect CrossWatch to providers. Tokens and URLs live here. Pairs use them for syncing and scrobbling.

Authentication is where you connect CrossWatch to providers.

You connect each provider at least once.

Each provider has a default profile.

You can also create additional profiles.

Use the Profile button on a provider.

CrossWatch will create the next available PROVIDER-P## profile ID.

In the UI these are called Profiles.

In config and API payloads, you will still see instance in key names. Example: instances, source_instance, provider_instance.

Pairs and Watcher routes can target a specific profile.

Guide: Profiles

Open Settings → Authentication.

Connect only what you use.

circle-info

Recommended first setup: 1 media server + 1 tracker. Validate one clean run. Then add more.

circle-info

New install? Stick to the default profile first.

Add Profiles only when the base setup is stable.

What we store (and what we don’t)

CrossWatch stores only what it needs to call provider APIs:

  • OAuth tokens, API keys, or user tokens

  • Provider URLs (for self-hosted services)

  • Provider user IDs and server IDs (when required)

CrossWatch does not store your provider password.

To remove access, revoke it in the provider.

Then reconnect in CrossWatch.

Generic connection flow

Each provider has its own details, but the flow is consistent:

  1. Click Connect (or Sign In).

  2. Approve access in the provider tab.

  3. Return to CrossWatch.

  4. Open Settings for that provider.

  5. Verify IDs and URLs. Use Auto-Fetch where available.

  6. Click Save.

circle-exclamation

Provider guides

Troubleshooting quick checks

  • Use a URL reachable from the CrossWatch host/container. Prefer LAN IPs over hostnames.

  • If OAuth uses a callback URL, it must match the provider app settings.

  • If libraries don’t load, check whitelisting. Then click Load Libraries.

Next steps

Last updated

Was this helpful?