XUI integration

Optional downstream integration

xOTT can operate its own subscriber access plane and native player, or supply authorized streams to an XUI workflow. XUI integration is not required for Access Lines, M3U, XMLTV, Xtream-compatible playback or xOTT Play. Do not confuse an XUI administrative User with a playback Line.

Connect a downstream panel

1. Open Administration → Integrations. Review Settings, Connections, Statistics and Logs.
2. Add a named connection with its actual Base URL, Access Code and API Key. Enter Server ID and default category/bouquet IDs where needed.
3. Test the connection before exporting. A login URL copied from a browser is not necessarily the correct API base.
4. Start and verify one saved stream, then export it and inspect the resulting mapping and downstream playback. Keep credentials out of shared screenshots.

Choose synchronization scope

Enable integration/auto-sync only when intended. The Sync Interval is shown in milliseconds. Review connection defaults, stream mappings and logs rather than assuming a successful connection test exports the whole library. Existing downstream entries and duplicates require deliberate mapping.

Export streams

Use stream/batch export controls for selected saved sources. Stable xOTT outputs shield the downstream panel from routine upstream manifest expiry. Retain mapping identity when migrating an input account. If a downstream channel is missing, check export status and mapping separately from xOTT subscriber entitlements.

Export events and stable slots

Use stable event-slot outputs when the downstream channel should retain its input URL while the scheduled match changes. Direct event export and scheduled event-import workflows have different lifetimes. Check source account, assignment, capacity, time zone and actual media readiness before expecting the downstream panel to auto-play it.

Diagnose the boundary

• Connection test fails: verify access code, API key, URL, firewall and timeout.
• Export succeeds but playback fails: test the same xOTT output from the downstream server.
• Wrong category/bouquet: inspect connection defaults and exported mapping.
• Duplicate entries: inspect existing mappings before re-exporting batches.
• A successful xOTT stream does not certify downstream headend, transcoding or subscriber configuration.