Services, accounts and routing

Adapters are not identical services

The release contains native service adapters, not a promise that every provider offers every action. Channels, events, VOD, authentication and DRM support vary by adapter, region, subscription and upstream changes. Use the actions actually offered on its service card. Do not treat a grey or unknown status as a confirmed authentication failure.

Add or pair an account

1. Open Content → Services. Find the service and choose the offered login or pairing action.
2. Choose a proxy before authentication if that account requires it. Review whether that proxy should also be used for streams.
3. For password login, enter credentials only in the panel. For pairing, open the provider’s activation address, enter the displayed code and wait for xOTT to finish polling.
4. Confirm the account appears under the service. Check its proxy assignment under Operations → Proxies.
5. Refresh only that account/service catalogue when you need updated content; provider refresh is not required for every table visit.

Pairing and reauthentication

Some providers return the username; others provide a stable account identifier. Re-pair the existing account using its edit/reauthentication action where offered. The modal should preserve its authentication method and assigned routing. Provider activation success alone does not mean xOTT has received the final token yet. If pairing stalls, inspect the account log rather than submitting codes repeatedly.

Proxy scope matters

A proxy working in your browser does not prove the same host, DNS, account region or path is working on a worker. Test the account and processing host actually involved. Avoid switching a live session between unrelated exit IPs.

SmartDNS stays service-specific

Configure supported SmartDNS integrations from Proxies and assign the intended service/account scope. DNS selection is passed through supported request and script paths; it must not be implemented by changing the host’s global resolver. It does not create a VPN, change every application on the server or guarantee that an unsupported provider domain will be routed.

Service outputs and defaults

The service Outputs modal groups linear/event outputs, event slots, account pins and stream defaults. Source account selection avoids ambiguity when a service has multiple accounts. Review scope before saving; service defaults do not replace intentional per-stream overrides.

Video, audio, subtitle and placement defaults are documented under Streams. Event rules and home/away feed mapping are documented under Events.

Disable, delete or replace?

• Disable a service when you want it excluded from ordinary active catalogue/event views without deleting its configuration.
• Use Manage stream source in Saved Library to move an output to another suitable account or source.
• Read the account-deletion warning and impact before confirming. Do not delete an expired account first if you intend to migrate its saved streams.
• Changing a provider password can invalidate sessions outside xOTT. Refresh or reauthenticate deliberately, then test one stream.

Custom integrations

Adapters declare capabilities and return structured results for supported actions. Not every adapter is required to implement login, events or VOD. The former public “API” page’s generic Python/DRM template was not a reliable integration contract; it has been replaced with the real player API guide. For a new provider, request an adapter review with sample non-secret metadata and a clear authorized use case.

Authentication succeeds but playback fails

• Confirm the account has rights to that channel/event in that region.
• Verify assigned proxy, streaming-use switch and the selected processing server.
• Probe the same saved source and read its log; distinguish authentication, manifest, license, transport and worker failures.
• Do not repeatedly relog all accounts or assume every HTTP 403 is a wrong password. Provider and CDN failures can occur after successful login.