An API login uses three fields: a server address, a username and a password. The app then asks the server for structured data, which is why you get a program guide, catch-up where the service offers it, and movies and series sorted into categories. A playlist login is a single link that returns a flat list of channels. It plays, but there is no structure behind it, so the guide is thin or absent and on-demand content may not appear at all. If the app looks empty of extras, check which login you used before concluding anything about the service.

1. 1API login: guide, catch-up, sorted movies and series
2. 2Playlist link: a channel list, usually without structure
3. 3Same service, two very different-looking apps

Because the failure message is vague and arrives at the moment you are least patient. A rejected login can mean a typo in a long password, a trailing space pasted from an email, an address entered without the correct port, an expired plan, or a connection limit already in use elsewhere in the house. Only the first two are yours to fix by retyping. The last one is the sneakiest: if someone else in the household is already watching and the plan allows one stream, the second device is refused in a way that reads like a broken account. Count your simultaneous streams before reinstalling anything.

1. 1Retype rather than paste, to kill trailing spaces
2. 2Check the address includes the port if one was issued
3. 3Confirm nobody else is using the connection you are counting on

A few, and they are identifiable. The app becoming sluggish or closing when you open the guide is a load problem: the visible channel list plus guide data outgrows the memory available, and hiding unused groups so the list stays under roughly 18,000 channels usually settles it. Playback that starts with audio but no picture points at a decoder mismatch, so switch between hardware and software decoding for that channel. Everything degrading on the day the app updated is a post-update regression, which is a distinct recurring cause worth ruling in early. Anything that behaves identically in a second player is not the app at all.

1. 1Guide crash: memory, so hide groups
2. 2Audio but no video: try the other decoder
3. 3Broke after an update: roll back and disable auto-update

Ask for the format of the credentials you will receive, the guide source, the number of concurrent connections and the refund terms, all before paying. A service that cannot state its login format clearly will not be quicker to answer when a channel group goes dark. Ask what uptime it publishes and convert the number: 99.99% works out to about 53 minutes a year. Then buy the shortest test available and set it up during live sport rather than a quiet morning. We issue standard credentials in about 5 minutes, allow unlimited installs, cap only simultaneous streams, and keep a 7-day money-back window on plans.

1. 1Login format, in writing, before payment
2. 2Concurrent connections matched to the rooms in use
3. 3Refund window and payout method stated up front