Questions & answers

A complete OTT / IPTV system: the admin panel (dashboard), the API server for viewers' apps, delivery of live channels, movies, series and radio, and a web player. We provide and maintain the system; resellers use it to give their customers the right to watch (lines).

• It does not collect money for you and has no payment gateway. The price for your customers, how you get paid and invoicing are the reseller's business (seeCON-01).
• It does not contact a reseller's viewers. The panel only sends email to panel accounts, never to a line.
• It does not keep personal data of a deleted customer and has no restore function (seeDATA-01).

1. The admin builds the catalogue (channels, movies, series, radio) and groups it intobouquets.
2. The admin creates apackage: bouquets + duration + number of connections + price in credits.
3. A reseller spends credits to sell the package → the system creates aline.
4. The customer enters the line's details in an app; the system checks the line (not expired, enabled, within its limits) and plays from a suitable server.

A reseller canviewthe lists of channels, movies, series, radio, bouquets and packages (when its group has the permission), but cannot add, edit or delete content. Content and packages are managed by the admin. A reseller decides what each customer may watch by choosing the package (and the bouquets, when the group allows it —PKG-05).

TheSupportentry of the sidebar opens the separate support site. The panel has no ticket system of its own. When you send a request, include: the username of the line (never the password), when it happened, the app / device, and the question code from this page if you already tried it.

The panel, the web player and this help page have a language switcher with 27 languages. English and Vietnamese are the reference translations; in the other languages a newly added screen can stay in English for a while. Email sent by the panel is currently in English only.

By design: a line is not a panel account. A customer only uses the line's details in an IPTV app, a set-top box or the web player. The other way round, a reseller account cannot be used to watch channels.

Menus and actions depend on thegroupthe admin gave your account. A page your group has no permission for is not shown in the sidebar and cannot be opened. Ask the admin for more permissions.

In the account area (profile → change password). Panel passwords are stored hashed; nobody can read them back — not even the admin. If you forget it, ask the account above you (your parent reseller or the admin) to set a new one.

The panel can be configured to end a session when its IP address changes, so a stolen session cannot be reused. Sign in again. This is an admin setting.

The panel limits failed sign-ins (configured by the admin). Past the limit you have to wait before trying again.

A demo account only shows the interface: it cannot change its password, edit its profile, create activation codes or do anything that cannot be undone.

The account above you switched it off: you cannot sign in to the panel and your API keys are refused. Lines already sold are not deleted. Contact the account above you.

Logs → Reseller Logs(when the group may view logs): every line or device created, edited, renewed, enabled / disabled or deleted, every sub-reseller created and every credit transfer — with the credits charged. You only see your own entries and those of the accounts below you; the log cannot be deleted (admin only). The credit ledger (CRD) remains the place to reconcile a balance.

The prepaid unit of the panel. Every sale (creating a line, renewing, creating activation codes, creating a sub-reseller) takes credits according to the package price or the group fee. A credit is not money and the panel does not convert it: what one credit is worth is agreed between you and the account above you.

Credits flow from the top down: the admin gives credits to a reseller, a reseller transfers them to a sub-reseller. Paying the account above you happens outside the panel.

Always those ofthe account that performs the action, even when the line is assigned to a sub-reseller below.

TheCreditspage: one row per movement, with the date, the amount, the balance afterwards, the reason and who did it. This is the ledger — the authoritative source for your balance.

The whole action is refused: no line is created and nothing is charged. A balance never goes negative.

No. Every sale request carries a request id (request_id); sending the same id again returns the earlier result. Creating the line and charging the credits always succeed together or are cancelled together.

No. Deleting a line refunds nothing, even when it has time left. The only exception: deleting anunused activation codethat the reseller created is refunded (CODE-08).

Yes: in the sub-reseller's edit form, enter a negative number in the credit transfer field. No balance can go below 0.

The package selector of the line form shows your own price. Through the API, thepricingaction returns your balance, the price of each package and how many you can afford.

Abouquetis a list of content (channels, movies, series). Apackageis the product you sell: one or more bouquets, a duration, a number of connections, output formats, locks, and a price in credits (official price and trial price).

A package can only be sold by the groups the admin selected for it. A package that is not meant for your group does not appear in the selector and is refused when sent through the API.

The admin can set anown priceper reseller for each package (0 = free). The own price applies to creating an official line, renewing, and official activation codes; it doesnotapply to trials.

No. The bouquets arecopied into the lineat the time of sale; editing the package afterwards does not affect lines already sold. A line receives the package's new bouquets at its next renewal / package change. (When the contentinsidea bouquet changes, every line holding that bouquet sees it at once. Deleting a bouquet removes its id from every line and package. Changing the global bouquet order only changes the order stored on sold lines when you tick the "apply to sold lines and packages" box; the set of bouquets of a line does not change.)

Only when your group hasAllow Bouquet Selectionon: you tick a part of the package's bouquets; nothing ticked = the whole package; bouquets outside the package are dropped. The price does not change.

The expiry date (today + the package duration), the number of connections, output formats, restreamer, device lock, forced country, forced server, ISP lock, bouquets. Values a reseller enters for these fields are ignored, except the bouquets (PKG-05) and the ISP lock when the group hasAllow Line Restrictionson.

A package that can only be sold for that kind of set-top box; it cannot be sold for an ordinary line or for the other device type. Conversely, a package must allow the device type before it can be used in the Add MAG / Add Enigma form.

You must pick a package your group may sell and have enough credits. Username / password: type your own (when the group allows it) or leave them empty to have them generated. An admin may also leave one of them (or both) empty when creating a line: the system generates 10 characters and shows them right after saving; theeditform still needs a username.

Your group hasAllow Username Change/Allow Password Changeoff: a new line gets generated values. When you may type your own, the minimum length is set by the group (8 characters by default).

In the line's edit form and in theGenerate play linkdialog of the Lines list. Line passwords are kept readable because IPTV apps and playlist links need them. A generated password is shown right after saving.

Some lines created by an earlier version of the panel only hold a hashed password. Such a linecannot sign inand the panel shows no password for it. Set a new password in the line's edit form and send it to the customer.

Enable / disable, reseller notes, contact, category template, owner (within your own tree); username and password when the group allows it; restrictions (IPs, user agents, ISP lock) when the group hasAllow Line Restrictionson; a new bouquet selection within the package when the group allows it. The package, expiry date, number of connections, trial flag, output formats, device lock and country cannotbe edited directly — they only change through a renewal / package change.

Two ways, one rule:

• theRenew (charged)button of the list: uses the line's current package;
• theExtend with packagefield of the edit form: pick any package you may sell (this is also how youchange package).

When you edit a line and choose a renewal in the same save, both areone transaction: if the renewal is refused (not enough credits, package not sellable), the edit isnotsaved either and no credits are charged. Correct it and save again.

• The line hasnot expiredand the new package iscompatiblewith the old one → the time is added to the current expiry date.
• The linehas expired, or the two packages are not compatible → counted from today; any remaining time is not kept.

"Compatible" is only checked when the new package has the compatibility check option on: both packages must have the same bouquets, output formats, number of connections, restreamer flag and device lock. With the option off they always count as compatible. New packages have the option on by default (the admin can switch it off); existing packages keep their setting. A MAG / Enigma line can only be renewed with, or changed to, a package that allows that kind of box.

A package change = buying one official period of the new package: the full price of the new package is charged (your own price if you have one), with no credit for the unused part. The line takes every property of the new package.

Disable: the customer cannot sign in or watch, running sessions are closed within about a minute; the subscription period keeps running; you can enable it again at any time.Delete: permanent, no restore, no refund (DATA-01). For a customer who pauses, disable — do not delete.

The customer is refused until the line is renewed (a line that is both expired and banned sees the "expired" clip, because expiry is checked first); running sessions are closed within about a minute. The line isnotdeleted automatically: renew it and it works again with the same username / password.

Yes: choose an account below you as the owner. The owner sees the line in its own list. The credits are still charged to whoever presses save.

Your own and those of every account below you. A line outside your tree does not exist for you (the answer is "not found").

For you to remember who the customer is (email, phone number, order number). The subscriber never sees them. They are erased for good when the line is deleted.

When the group has the permission:Logs → Line Activityshows the viewing history of each line, andLogs → Live Connectionsshows every open connection of the lines in your tree (which line, which channel, from which address) with a button to close it. Live Connections only opens when the admin switched on, for your group, the option to view customers' connection history (theclient connection logsbox of the group form); you never see connections of a line outside your tree.

A line that belongs to an activation code is hidden from the list by default until you filter for it (CODE-02).

Yes. TheExpires onfield of the line form is a dateand timein the panel's time zone, so a line can expire at a specific hour. Opening the form and saving without touching this field keeps the expiry to the second — editing a note or the bouquets does not give an hourly trial line extra time. A value that cannot be read is reported at the field itself and never turns into "never expires". The mass edit page still takes a date, read as the end of that day.

Whenallof these hold: the admin has not switched trials off for resellers; the package has a trial period; your group hasAllowed Trials> 0; your credits are ≥ the group'sMinimum Trial Credits; and the number of trial lines you created within the counting window has not reached the quota.

As set on the group:day= the last 24 hours,month= the last 30 days. Example, a quota of 5 / day: at most 5 trial lines in any 24 hours. An older trial frees its slot when it leaves the window.

Exactly the package's trial price (usually 0). A reseller's own price does not apply to trials.

One of the conditions ofTRI-01is not met; the form states the reason next to the box.

Renew the line with a package: the line gets an official period and is no longer a trial. Username and password stay the same, the customer does not have to set anything up again.

No. A trial is grantedonce, when the line is created; an existing line can only be renewed with an official period (TRI-05). To let a customer try again, create a new trial line (it counts towards the trial quota).

Lines → Generate play link: choose the format; the link is built with the line's username and password. Through the API,get_linereturns the links ready-made:m3u,m3u_hls,xmltv,player_api,web_player.

Any app that supports theXtream Codes API(IPTV Smarters, TiviMate, XCIPTV, GSE…): enter the server address + username + password. For an app that only takes a playlist, use theM3Ulink.MAGboxes use the portal,Enigma2boxes use a playlist / plugin. Without any device, use theweb playerin a browser.

MPEG-TS: fast channel switching, suits IPTV apps and set-top boxes.HLS: works well in browsers, on Apple devices and on unstable networks. A line can only use the formats its package allows; a link in a format that is not allowed is refused.

m3u_plus(with logos, groups, EPG ids — the recommended default), plainm3u, the types for Enigma2 / DreamBox / GigaBlue / Octagon / MediaStar / StarLive, and simple list types. Choose one in the Generate play link dialog.

Xtream apps fetch it by themselves. For an M3U app, use the line'sXMLTVlink (anm3u_plusplaylist already carries the EPG address).

Yes, on the channels for which the admin enabled archiving; apps show a catch-up icon on those channels.

At/player/on the API server (theweb_playerlink). Sign in with the line's username / password, or with an activation code.

No. The password is part of the link and is stored in the app; after a password change the customer has to enter it again / get a new link. This is also how you cut off someone using a line without permission.

Yes: setYour own play addresson the API key page (or with theset_play_baseAPI action). You point the DNS of the domain to the panel's API server,andthe operator has to configure their side; tell the admin before you use it. The address applies to the links the API returns to your system.

Technically they share one line, so they share itsnumber of connections(SEC-01) and may run into the second IP rule (SEC-03). Every customer should have a line of their own.

Devices → Add MAG / Add Enigma: enter the MAC, pick a package. The system sells a new line and attaches the device in one step; the device signs in by its MAC, nobody has to type a username / password. Credits are charged exactly as for an ordinary line.

In the device form, choose the customer'sexisting lineinstead of a package: the device ispairedwith that line, free of charge. The customer keeps using the line in the app; the box follows the line's package, expiry, bouquets and status.

Theysharethe connection limit: the app and the box are one subscriber.

Renew its line (the link is on the device form). For a paired device, renew the customer's line — the box follows by itself.

Edit the MAC on the device. If the line has the device lock on, clear the recorded serial number / device id so the new box can register.

Yes. Deleting a device deletes its line too (with its connection history and pending events), as in the old panel. To keep a line that was paid for, use theConvert to linebutton: the device is removed and the line becomes an ordinary line. When you delete a customer's line, a paired device lives on independently with a line of its own.

Its ownMAGboxes, yes: send a message to the TV, play a channel, reload the portal, reboot, close the line's connections (the group needs the permission to view customers' connection logs), reset the recorded ISP and reset the STB lock. X-Plugin commands and screenshots ofEnigmaboxes, banning a device and moving a device to another line are for the admin only. Enabling / disabling a reseller's device enables / disables its line; a reseller cannot liftBannedfrom a device.

Selling access as a code (a scratch card, a code sent by message): the customer enters the code in an app or in the web player and can watch, without a username / password. The periodonly starts when the customer activates the code for the first time.

Active Codes → New: choose the package, the quantity (1–500 per batch), the code length (6–24), the digits-only option (easy to type with a TV remote), the trial option. Credits are chargedat creation= package price × number of codes. Every code comes with a line of its own, locked until activation.

Capital letters and digits without the easily confused ones (0, O, 1, I); or digits only. A customer typing lower case is still accepted.

One. The code is tied to the first device that activates it; another device entering the same code is refused. That device may enter the code as often as it likes, the line's sign-in details do not change.

Reset deviceon that code; the new device can then activate it. No time is added to the period.

Entering several different wrong codes in a row gets the IP address blocked for a while (SEC-08).

On theActive Codespage, tick the code, choose theExtend (days)action and enter the number of days. Only anactivatedcode gets days added (an unused code has not started its period yet); a code that is still valid is extended from its current expiry date, an expired one from now. This action charges no credits. Through the API:extend_active_code.

Anunusedcode created by the reseller: fully refunded, with a row in the credit ledger. Anactivatedcode: no refund.

TheBatchespage shows total / ready / activated / disabled for each batch and exports a TXT file (one code per line). Bulk actions: enable, disable, reset device, delete.

Yes, like every line sold with that package: number of connections, output formats, bouquets, device lock, restreamer and also the package'sforced country(SEC-07). A customer who activates a code from a country outside the allowed list can activate it but is refused when playing.

It is the number of devices watchingat the same timewith one line. 0 = unlimited. Opening the channel you are already watching again from the same device does not count as another connection.

By default: thenewconnection gets in and theoldestone is closed (preferring a connection from the same device, then from the same IP). The closed player stops within about 30 seconds. The admin can switch torefusing the new connectioninstead of closing an old one.

When the admin has it on: while a line is being watched from one IP, a live connection from another IP is refused. The rule can be limited to lines with few connections (for example lines with 1 connection; a line with unlimited connections is only bound when the threshold is 0). WithMatch The Address By Networkon, addresses of the same /24 network (IPv6: /64) count as one viewer. This is a tool against account sharing.

When the group hasAllow Line Restrictionson: theAllowed IPsfield (an IP, a CIDR range or a domain name, one per line; a domain is looked up at connection time, so a dynamic IP still works) andAllowed User-Agents. Empty = everything allowed. Note: these restrictions block atplayback; the app still signs in and shows the channel list.

The line remembers the internet provider of its first connection and refuses use from another provider. When the customer changes provider, switch the ISP lock off and on again to record the new one. It does not apply to MAG boxes.

It ties the line to the first set-top box that signs in (serial number, device id); another box is refused. Decided by the package.

A line can only connect from its forced country (ALL= anywhere). When it is empty, the panel's general list of allowed countries applies. A customer who travels abroad or uses a VPN may be refused for this reason.

• Automatically: failed sign-ins from one IP with many different usernames / activation codes in a short time, or a flood of requests. An automatic block lifts itself after the time the admin configured (60 minutes by default).
• Manually: the admin blocked the IP / IP range; this does not expire.

While an IP is blocked,noline can connect from it. Repeatedly mistyping the same username does not cause a block.

The admin can block byUser-Agent(app), byinternet provider (ISP)and byASN(for example hosting / VPN ranges). A line for which the admin switched on "bypass UA" skips the app block list.

A line for a partner who pulls the streams to redistribute them. It is exempt from the connection limit, the second IP rule, the automatic end of long sessions and ASN blocking. Decided by the package / the admin; not meant for ordinary viewers.

The admin can set a maximum duration for a continuous session; past it the session is closed and the customer presses play to continue. A session that loses its signal for about 90 seconds also counts as closed.

• TheTheft Detectionpage (when the group has the permission): ranks lines by the number ofdifferentmovies / episodes watched in 1 hour / 24 hours / 7 days, with the number of different IPs — an unusually high line is suspicious.
• The line's activity page: shows the IPs and devices in use.
• What to do: change the line's password (PLAY-08), switch on the IP restriction / ISP lock, or disable the line.

When your group hasCan Create Sub-Resellerson and at least one group inGroups for sub-resellers. Each creation charges the creation fee (credits) set on the group. A reseller tree is at most 5 levels deep.

You choose a group from the list the admin allows; that group decides the sub-reseller's permissions, sellable packages and trial quota.

Email, name, password, status, group (from the list), notes, transferring / taking back credits, and every line below them. You cannot change their role or owner.

Nothing: every account only sees what is below it, never the levels above or other branches.

The group needsCan Delete Userson. The remaining credits, the lines and the child accounts move tothe account that deletes. The customers' lines keep working. The personal data of the deleted account (username, email, name, password, API keys, notes) is erased; that username and email can be used again.

When the admin enabled the welcome email: the new account receives its sign-in name and a sign-in link. The emailnevercontains the password — you send them the password yourself.

To reorder, rename or hide the categories (live, movies, series, radio) a customer sees in the app — per line, without touching the panel's own categories.

All content of that category is hidden as well from the app and the playlist of the lines that use the template.

Yes, at once for every line the template is assigned to. When a template is deleted, its lines return to the default layout.

See: your own and those of accounts below you, system templates, and templates shared by the levels above. Edit: only your own and those below you. To adjust a system template,duplicateit and edit the copy.

The custom category order does not apply to the movie / series part of an M3U playlist (names and hiding still apply). Apps using the Xtream API get everything.

For your own system (web shop, billing, bot) to sell and manage lines / sub-resellers without opening the dashboard. Address:{API}/reseller/v1, authenticated with theX-API-Keyheader. Full documentation is at/docs/on the API server.

TheAPI Keypage. A key is shownonce, when it is created — copy it right away. If you lose it, create a new key (the old one stops working).

Better not. Create anadditional keyper system: give it a name, limit the IPs / CIDRs that may use it, optionally make itread-only(list and view only), and revoke it on its own without affecting the other keys.

Every rule of the dashboard (group, own price, trial quota, tree scope) applies through the API in exactly the same way.

No, as long as you send the samerequest_idfor the same transaction: the system returns the earlier result. Therequest_idof a renewal isbound to that line: reusing it for another line returns a conflict error (HTTP 409) and the other line does not change — generate a newrequest_idfor every transaction.

The API Key page has a table ofrecent API calls(30 days): action, result, error code, calling address, connector name. Parameters are never recorded.

The panel tells your system when something happens, so you do not have to keep asking. Events:line.created,line.renewed,line.enabled,line.disabled,line.deleted,line.expiring(3 days ahead),line.expired,credits.low(below the threshold you set). The receiving address must be https and reachable from the internet.

Every notification carries the signatureX-Xtream-Signature: sha256=HMAC(secret, timestamp.body); the secret is shown once, when the endpoint is created. A webhook never contains a password.

Every notification is tried 3 times; an endpoint that fails 20 deliveries in a row is switched off. Fix your side, useSend test, then create the endpoint again if it was switched off.

Yes, but only to the owner of the line (you and the levels above you in the tree). Do not store line passwords in logs or send them over an insecure channel.

Yes, when you sendpackage_idwith it (the old namepackageis accepted too): besides the edit, the action sells one official period of that package exactly likechange_package— same price, samerequest_id, and the answer carriescredits_charged. Edit and renewal are one transaction: when it is refused (not enough credits, invalid package,trialsent along) nothing changes.edit_linewithouta package only edits username, password, contact and notes and does not touch the package or the expiry.

Not as it is. The API keeps the familiar action names but is a new interface: the address/reseller/v1, an API key created in this panel, write actions sent with POST, errors returned as an HTTP status with anerrorfield, and the result of creating a line indata.line. Use the documentation at/docs/or a ready-made connector (CON-02).

Withyour ownsystem and payment gateway. The panel does not process payments. A connector links your shop system to the panel: the customer pays on your side → the connector calls the Reseller API to create / renew the line.

WHMCS, Blesta, WISECP, HostBill, ClientExec, FOSSBilling, Paymenter, WordPress (WooCommerce / Easy Digital Downloads), Odoo, PrestaShop, OpenCart, Magento, Dolibarr, ERPNext, and a "webhook bridge" for Shopify, Upmind and Invoice Ninja.

SidebarResources → All Connectors: every connector has a description, the connection details, the installation steps, aDownloadbutton and the SHA-256 of the file to verify it.

It differs per connector, and each connector's page says so: some ran inside the real platform (for example WordPress + WooCommerce, Odoo, FOSSBilling, Paymenter), others only had their core exercised. Read the "how it was tested" line and try it in a test environment before selling for real.

A connector only calls the Reseller API withyourAPI key — it can do exactly what you can do, nothing more. The source code is open for you to read and check. Give every connector a key of its own with an IP limit (API-03).

Lines (create, renew, change package, suspend, delete) and sub-reseller accounts with credits.

Integrate it yourself with the Reseller API (API-01) and webhooks, or send a request through the support channel.

No. Deleted is gone: the line's details (username, password, contact, notes), its connection history (IPs, devices, what was watched), the set-top boxes attached to the line and its activation code. There is no recycle bin and no restore function or API. When the customer comes back, create a new line.

Only ananonymousstatistical record for the operator (new or returning customer, which packages are popular). It holds nothing readable about the customer and no reseller, connector or API can reach it.

No. Database backups only exist to rebuild the system after an incident and are held by the operator; they are not used to undo a deletion. Old backups are rotated out, so deleted data disappears from them as well.

A line password has to be typed into apps and is part of the playlist link, so the panel keeps it readable for the owner of the line. Panel account passwords are only stored hashed.

You, the accounts above you in your tree, and the admin. Other resellers and the levels below you cannot.

Never. The customers of a line belong to the reseller; you contact them through your own system.

In two ways: a daily summary email of the lines about to expire (when the admin enabled it; 3 days ahead by default), and theline.expiring/line.expiredwebhooks for your system.

Usually one of the playback locks (rows 5–9 ofFIX-01): signing in and the channel list do not check the IP / app, only playback does. If onlyonechannel fails on every line → the source channel has a problem; tell the admin the channel name and the time.

Check the bouquets of the line (PKG-04,PKG-05) and the category template assigned to it (CAT-02). After a change, ask the customer to reload the list in the app. A channel the admin just added appears after about half a minute; if a channel is in the bouquet and no line sees it, the admin may have taken that channel off air.

Try in turn: another channel (one channel or all of them?) → another network → another format (HLS instead of MPEG-TS) → another app. Every channel fails on every network → tell support the username, the time and the channel.

An M3U app needs the XMLTV link added (PLAY-05). A channel without EPG at the source shows no schedule.

In turn: no package chosen · the package is not for your group (PKG-02) · not enough credits (CRD-05) · the username is taken or shorter than the minimum (LINE-02) · the trial quota is used up (TRI-01).

429: the line is downloading too many playlists / EPG files at once — wait and try again. 404 page: the system answers 404 foreveryrefusal (wrong details, expired, locked, over a limit) so the reason is not revealed to strangers; check withFIX-01.

Your group has no permission for that page (ACC-02).Live Connectionsadditionally needs the admin to switch on the option to view customers' connections for the group (LINE-15).

Email is only sent when the admin configured a mail server and enabled that kind of message; the account must have a real email address. Check the spam folder.