A panel is a price list with an order queue behind it. You choose a row, paste a link to the channel or the post, name a quantity between that row's own floor and ceiling, and the balance on your account pays for it; from there the order is ours to fill and yours to watch. Where panels differ is whose services sit behind the rows, what the rate is before anybody marks it up, and whether an order can be placed by software rather than by hand. Those three are what this page covers.
The reseller's route through this page
- What an SMM panel is, and who is behind this one
- Setting a margin you can defend
- Telegram Views SMM Panel, seen from the reseller's side
- What the price list actually says
- One key, one endpoint, a short list of actions
- Your own domain, your own customers
- Before you resell: the short answers
What an SMM panel is, and who is behind this one
The word panel covers three faces of the same thing: the website you can click through, the API a machine can call, and, if you want one, a storefront of your own. All three read the same catalogue and draw on the same balance, so a rate is the same rate whichever way the order arrives.
What sits behind that catalogue is what a reseller is really buying. Here it is us: 1,134 rows of Telegram, X (Twitter) and YouTube services, supplied by TGLUX rather than bought in and marked up on the way through. That is why there is no retail page on this site with a trade door round the side. The price list is the trade price.
Setting a margin you can defend
Think of the price list as the cost column of your own spreadsheet. A row here at $0.0025 per 1000 is what an order of that row costs you; whatever your customer pays above it is yours. Set it once as a percentage across everything, then override the handful of services that sell most, because those are where a point of margin is worth arguing about.
The override has a safety catch. A price you store is never allowed to sit under our own cost, so if a base rate moves up after you set it, the order is charged at the floor rather than at a loss - and the figure your storefront quotes comes from the same rule as the charge, so the two cannot drift apart.
Telegram Views SMM Panel, seen from the reseller's side
For reselling, Telegram views SMM panel has to be cheap, dependable and automatable. TGLUX is the provider rather than a middleman, so the price list is wholesale: Telegram views SMM panel from $0.0025 per 1000, a full SMM API v2 for wiring orders into your own bot or storefront, and child panels if you want to run the shop under your own brand on your own domain. Your customers see your prices; you see ours.
What the price list actually says
Rates are per 1000 and in this category they cover the full distance from $0.0025 to $1.25 across 19 rows, so a sample of the cheapest alone would tell you nothing about the rest. The rows below are spread from the cheapest to the dearest, which is also roughly how a reseller's own price list ends up looking once the countries and the post counts are in it:
- Seen Post - from $0.0025 / 1000 (min 10, max 1,000,000)
- Seen Post [10 Future Post] - from $0.025 / 1000 (min 10, max 1,000,000)
- Seen Post [Last 20 Post] - from $0.05 / 1000 (min 10, max 1,000,000)
- Seen Post [Last 50 Post] - from $0.125 / 1000 (min 10, max 1,000,000)
- Seen Post [100 Future Post] - from $0.25 / 1000 (min 10, max 1,000,000)
- Seen Post [500 Future Post] - from $1.25 / 1000 (min 10, max 1,000,000)
Rates move with the catalogue - the live list is on our Cheap Telegram Views page.
When you copy these rows into your own price list, keep the wording after the service name. It is where a row says what it covers, and a customer who sees the same words you saw is a customer who does not open a ticket asking why.
One key, one endpoint, a short list of actions
The two requests worth getting right are the service list and the status poll. The list is the one to cache: it changes when the catalogue changes, not between orders, and building your own price table from it once is cheaper than asking for it per customer. Status is per order, and what comes back is rolled up - one order, one status, one figure for what is still owed, whatever happened underneath.
Polling harder will not get you a newer answer. Order state is refreshed on our side on a fixed cycle, so a client asking every few seconds sees the same reply as one asking sensibly and only the rate limit notices the difference. That limit, and the cap on ids per status call, are both at https://smmtglux.com/api-docs.
Your own domain, your own customers
A child panel is your own shop at your own address: a domain of yours pointed here with an A record, or a subdomain of ours if you would rather not touch DNS at all. It carries your name, your theme and your prices, and your customers register on it rather than on our site - their accounts exist on your panel and nowhere else.
Behind it sits a wallet. Each order your customers place takes our base cost out of that wallet and writes a ledger line for it, so the margin is visible order by order instead of being reconstructed at the end of a month. The panels themselves are free at the moment: no monthly fee, and nothing taken per order beyond the base cost.
Before you resell: the short answers
Can the panel show prices in my own currency? Yes, as a display setting with a rate you choose. The wallet and its ledger stay in the base currency, so what an order costs you does not move when the displayed figure does.
Does the API take drip-feed orders? Only on a service whose dripfeed flag in the API's service list is true. Any other drip-feed request comes back refused with a reason rather than being delivered as one bulk order, so nobody is charged for a schedule that will not run.
Will my customers see your name anywhere? No. The brand, logo, theme and links on a child panel are yours, our own contact channels and analytics are not loaded there, and our payment gateways are switched off so that nothing can route a payment to us instead of to you.
Are the order numbers the same in the API and on the site? Yes. The API takes and returns the numbers shown in your dashboard, so a customer's confirmation and our order list point at the same order.
Why does an API error arrive with HTTP 200? That is how the standard SMM API v2 behaves: every reply is a 200, and a failure is an error field in the body. Read that field rather than the status code, or every failure will look like a success.
Open an account and read the price list
Deposit the minimum of $5, place a single order through the API rather than the website, and read what comes back. If your client handles that reply correctly, it will handle the rest of the catalogue - the reference is at https://smmtglux.com/api-docs.