An order here is three facts: a service id, a public link and a quantity. You send those, your balance is charged at the rate on the price list, and the job joins the queue, reporting a start count and then progress until it closes. That is the whole mechanic, and everything a panel adds sits around it - a catalogue to pick the id from, a balance to pay from, an API so a machine can do the picking instead of a person. What follows is how TGLUX handles each of those, and what the wholesale side of it costs.
What this page covers
- What an SMM panel is, and who is behind this one
- Cost in, price out, margin kept
- Telegram Auto Views SMM Panel, seen from the reseller's side
- Live rows from one Telegram category
- What the reseller API does, action by action
- A storefront we host under your name
- The questions that come up on a first integration
What an SMM panel is, and who is behind this one
An SMM panel is a catalogue with an order queue attached. Each row is a service: a numeric id, a rate per 1000, a floor and a ceiling on quantity. You pass a row id, a public Telegram link and a number; the balance on your account pays the rate, and the order is queued, sent on, and reported back with a start count.
Who stands behind the rows is the part worth asking about. TGLUX is the provider here - the Telegram, X (Twitter) and YouTube services in this catalogue are ours and we supply them wholesale. Our customers are the people reselling them, which is why the price list is the wholesale one and not a retail page with a trade counter at the back.
Cost in, price out, margin kept
The arithmetic is deliberately dull. We charge the rate on the price list, from $0.0125 per 1000 in this category; you charge your customers whatever you have set; the difference is yours, and it settles order by order rather than at the end of a month. There is no fee for placing an order and no volume you have to hold to keep a rate.
Where resellers lose margin is usually not the rate. It is crediting a customer's balance against money that has not arrived yet: balance you grant is a promise you fund, and it turns into real cost the moment that customer spends it.
Telegram Auto Views SMM Panel, seen from the reseller's side
Every resold order moves two figures: your customer's balance at your price, and the wallet behind your panel at ours, from $0.0125 per 1000 on the rows quoted here. Both are written down order by order, and both are reversed together when an order is canceled or only partly delivered, which is why the margin on a busy day is a number you can read rather than one you have to rebuild.
Live rows from one Telegram category
The whole catalogue is 1,137 live services in 54 categories across Telegram, X (Twitter) and YouTube, and the rows are quoted per 1000 in the base currency. Nothing is added at checkout. One category is enough to show the shape of a row - an id, a rate, a floor and a ceiling - so these are the cheapest currently listed in the category this page takes its figures from:
- 🇮🇷 Iran Post Views [Future 5 Post] [Include Static] - from $0.0125 / 1000 (min 10, max 1,000,000)
- 🇮🇷 Iran Post Views [Future 10 Post] [Include Static] - from $0.025 / 1000 (min 10, max 1,000,000)
- 🇮🇷 Iran Post Views [Future 15 Post] [Include Static] - from $0.0375 / 1000 (min 10, max 1,000,000)
- 🇮🇷 Iran Post Views [Future 20 Post] [Include Static] - from $0.05 / 1000 (min 10, max 1,000,000)
- 🇮🇷 Iran Post Views [Future 30 Post] [Include Static] - from $0.075 / 1000 (min 10, max 1,000,000)
- 🇸🇦 Arab Post Views [Future 5 Post] [Include Static] - from $0.075 / 1000 (min 10, max 1,000,000)
Rates move with the catalogue - the live list is on our Telegram Auto Views for Future Posts page.
Read the bracketed part of a row name before you read the rate. That wording is the provider's own and it is where the scope sits - one post or a run of them, one country or a mix - and scope is what a rate difference inside a single category nearly always means.
What the reseller API does, action by action
What the API refuses is as worth knowing as what it accepts. Ask for a drip-feed on a service that does not support one and the request comes back refused, with a reason, rather than quietly becoming a single bulk order that is charged in full - that failure costs a reseller a customer rather than a few cents, which is why it is an error and not a silent fallback.
Failures further upstream are kept away from you as well. What you get is a plain message, not somebody else's raw error text, so nothing about our own supply reaches a customer's screen by travelling through your integration. The strings each action can return are listed at https://smmtglux.com/api-docs.
A storefront we host under your name
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.
The questions that come up on a first integration
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.
What do I need to start using the API? An account, a balance, and a key generated on your own API page. The key is shown once and kept only as a hash, so losing it means issuing a new one rather than reading the old one back.
Can I close a child panel later? Yes. The delete form lists what goes with it - the storefront, its customer accounts and their balances - and asks you to type the domain to confirm. What is left in the wallet is returned to your account, up to the amount you funded yourself.
Do I need a server of my own for a child panel? No. The panel runs here. A domain of yours needs an A record pointed at us and nothing else, and a subdomain of ours needs nothing at all.
A test order first, then the integration
Open an account at TGLUX, put the minimum of $5 on it, and place one small order on a service you intend to sell. Then read the price list at https://smmtglux.com/catalog with your own margin in mind, because that figure is what everything else here depends on.