Client protocols
Every subscriber's credentials produce all of these automatically — the client page shows ready-made links per account.
| Client | URL | Tier |
|---|---|---|
| Xtream Codes any Xtream Codes player, e.g. TiviMate, OTT Navigator | /player_api.php | Free |
| M3U playlist | /api/channels/m3u?token=… | Free |
| EPG (XMLTV) | /xmltv.php?token=… (or ?username=…&password=…) | Free |
| Stalker / MAG | http://host:8095/stalker_portal/c/ | Pro |
| Kodi (HTSP) | host + port 9982 | Pro |
| Enigma2 / VU+ | /api/enigma2/bouquet?username=… | Business |
| Plex / Emby / Jellyfin | /discover.json (HDHomeRun) | Off by default (setting hdhr_enabled; LAN only) |
| Web player | /tv · account portal at /account | Free |
Free includes the basic Xtream Codes API (live TV and the M3U playlist). The full Xtream Codes API is Pro and up, like the VOD library (see Licensing).
Links generated for a subscriber carry their stream token where the password would be; both still sign in.
The BGPVR Kodi add-on (BGPVR Setup 1.2.0 and newer) signs in with the viewer's phone: Kodi shows a QR code and a code like ABCD-EFGH, the viewer approves it in My Account (or the BGPVR Player phone app), and the box gets a sign-in of its own, never the account password. It is listed in Devices as Kodi and is signed out there like any TV; its play links carry that device's own credential. Typed sign-in (server, username, password) stays, and Advanced Setup (pvr.hts, HTSP port 9982, recordings, Pro) always uses it. Kodi also runs on a LibreELEC box (a Raspberry Pi 4/5 or an x86 mini-PC): see "Kodi on a LibreELEC box" in the subscriber help (/help#kodi). Both BGPVR add-ons come from the BGPVR repository at k.bgpvr.com: BGPVR Setup (live TV and the TV guide) and BGPVR Live TV (films and series). A LibreELEC box uses the same repository; LibreELEC downloads IPTV Simple Client itself and the viewer restarts Kodi once. Simple Setup needs a package with Kodi/M3U access.
BGPVR Player for Linux (beta) runs on 64-bit Linux PCs, as an AppImage or a .deb. When the Linux app is switched on for your server, viewers find it in My Account › BGPVR App › Get the app. The same beta is also in the BGPVR apt repository (apt.bgpvr.com, updated with the system), in the Snap Store beta channel (snapcraft.io/bgpvr-player) and on GitHub (github.com/bgpvr/linux); the LGPL source sits next to the downloads. Their install steps are in the subscriber help: /help#linux.
Generated links carry a separate token instead of the password, so Clients → Edit User → Streaming Links → “Reset Streaming Links” (or the same button in Access Links) cancels every copy that carries the token (the M3U link and the links on the subscriber's account page) at once, while the subscriber keeps their password. A URL that contains the password, such as one copied from the console's Access Links modal, keeps working until you also change the password. Kodi (HTSP) is not affected.
Set Stalker stream base URL to include the reachable port, e.g.
http://mag.example.com:8095. Older MAG firmware cannot set cookies
over HTTPS, so use HTTP for the portal. This setting affects MAG/Stalker only —
the app and web player use separate endpoints. MAG and TH boxes also accept the bare
server address (http://host:8095/) as the portal URL; the
/stalker_portal/c/ path is optional. The portal is in use on MAG 250, 254,
322, 420 and 524 and on TH100 and TH300.
It exposes a full channel lineup with no credentials, and enough simultaneous requests will pin every tuner and black out live TV. Enable it only if you need Plex/Emby/Jellyfin, and keep it on the LAN.