Provider scripts that belong to an operational platform
Use included, capability-aware IPTV and OTT adapters with account management, routing, saved channel identities and downstream delivery—not disconnected scripts alone.
Start Free Trial Read setup guideWhat an adapter can provide
A provider script connects supported account/catalogue/playback actions to xOTT’s universal workflows. Some services expose linear channels, others sports events or movies/series; an adapter is not required to implement actions its provider does not support. The service card presents its available authentication and content actions.
Included adapters cover a broad provider catalogue, including DAZN, ESPN, DirecTV, Hulu, Sling, Viaplay, SkyShowtime and other regional services. Availability depends on region, account rights and upstream changes. Brand names identify integration targets, not endorsement or a bundled subscription.
Keep regional routing attached to the right account
Choose the intended proxy during supported authentication/pairing and review whether it should also be used for streaming. Account requests, source acquisition, processing workers and public delivery are different scopes. A proxy working in a desktop browser does not prove a worker reaches the same provider path.
Supported SmartDNS is service-specific. It is not a reason to rewrite the global server resolver or change the network behavior of unrelated applications.
Refresh a catalogue without recreating outputs
Filter Live Streams by service/account before refreshing and saving channels. Saved Library retains output identities, categories and operator settings. If an account expires, use Manage stream source to replace it deliberately; optional ordered backups have their own compatibility and recovery rules.
For events, map competition/team rules to stable slots and inspect distinct feed identities. For VOD, download/import into the Library, verify the file and publish only to the intended package.
Included does not mean permanently guaranteed
Providers change APIs, catalogues, account policies and playback requirements. A maintained integration needs evidence from the affected account and exact failed action—not blind repeated login attempts. Use the full-feature trial to validate your own provider mix.
For a new adapter request, provide a clear authorized use case and non-secret catalogue/action requirements. Do not send passwords, provider tokens or device material through public support channels.
Plan, configure and verify
Services, accounts and routing · Configuration map · Release history
Test your own sources and infrastructure
Use the full-feature trial with authorized accounts and representative clients. Verify the workflow before scaling.
Create account Plans and worker licensing