Signing in with a provider account (Xtream API) on Xbox

If your provider handed you a username, a password and a host, you have an Xtream API login. Use it rather than the M3U export the same provider will also give you. The export is a snapshot. The API is a conversation, and three things fall out of that difference.

Where the credentials go#

Not on the console. The Xbox has no field for a host, a username or a password, and the sources screen there says what it is: read-only, synced from the web console.

Open the web console, go to Sources, add an Xtream source, and give it the three values your provider sent you. They usually arrive looking like this:

Host      https://provider.example.com
Username  your-username
Password  your-password

Each value is accepted up to 2048 characters, so length is rarely why a login fails. Save it. The console picks the source up on its next sync, as one of the 13 kinds of account state that follow you between devices, and you never type any of that on a controller.

There is a security reason to prefer this direction as well as an ergonomic one. Credentials entered in a browser go into your account once. Credentials typed on a shared living-room screen are typed in front of whoever is in the room.

What the provider's API gives you that a file cannot#

A playlist export is a list of URLs frozen at the moment it was generated. The provider's API answers questions, and the client asks it several. The whole Xtream API is one endpoint taking an action parameter, and 15 actions cover everything below.

The first is the catalogue itself, categories included, which is what lets the console show you your provider's groups instead of one flat wall of channels. The second is the archive: the provider can say which channels keep a rewindable window and how many days deep it goes, which is the whole basis of catch-up. See what catch-up and timeshift actually are.

The third is the one people discover the hard way. The provider reports how many simultaneous connections your subscription allows. That number is not decoration: it is why a channel that plays on the Xbox refuses to play on the laptop at the same time, and why multiview is careful with it.

Multiview counts that budget before it assigns a tile, not after. Ask for a 3x3 grid of 9 tiles against a subscription that allows 2 connections and the picker stops offering channels from that source once the second one is spoken for, rather than starting 9 streams and letting the provider reject 7 of them. That is a deliberate choice about where the failure happens. Provider connection limits goes through the accounting in detail.

The stream format setting#

An Xtream source has a Stream format control. It currently changes nothing, and that is our mistake rather than the provider's. It normalizes its value, saves it and reloads it, and no URL builder and no playback code reads it back.

Whatever it is set to, the client asks for a live URL ending in .ts, in this shape:

https://provider.example.com/stream/12345.ts

The real address also carries your login, which is why it is not shown here. That is what we request, not what a provider server returns. A provider is free to redirect that request to an HLS manifest, and some do; the client does not probe for it. MPEG-TS or HLS has the argument and the measurements.

What is not on the console yet#

Catch-up is the honest gap. It shipped on the desktop head first, and the console page for it is still outstanding work. So a provider that offers a 7 day archive gives you that archive in the Windows app today, and on the Xbox you get live channels and the schedule without the rewind. Even on Windows the reachable window is bounded by guide retention, which keeps 1 day back by default, rather than by the provider's advertised 7 days.

The schedule itself is there. On the console it lives inside Live TV rather than as a separate destination: open a channel, bring up the schedule layer, and the bumpers move you a day at a time. The standalone Guide screen in the app navigation is still a placeholder.

Being specific about that beats the alternative. An article that implied full catch-up parity would cost you an evening of looking for a button that is not there. Catch-up TV on Xbox says what works today and what is coming.

If the provider login will not connect#

The most common cause is not the provider at all. The credentials are right but the account is at its connection limit, because something else is still holding a connection. Providers do not always time out a dropped session immediately, so a stream closed a minute ago on another device can still count. When the provider does answer and refuses, the app says why: an account marked expired, disabled or banned, or a rejected password, is reported as that rather than as a connection problem.

If the login fails on one machine and works on another on the same network, the difference is on that machine rather than at the provider. A playlist that will not load walks the rest.