Up to 100 orders a month free

SMM panel with an API for resellers

A ready panel whose API runs in both directions: your resellers send orders to you with their own key, and the panel itself buys from providers. Neither side has to write an integration.

Start free View demo

In short

Pay as you go: the plan is set by the number of orders per month, counted separately for each panel.

Free: $0 forever up to 100 orders / month
Starter: $12 per month 101 - 1,000 orders
Basic: $25 per month 1,001 - 10,000 orders
Growth: $40 per month 10,001 - 100,000 orders
Scale: +$40 per +100,000 each next 100,000

The key distinction

A panel has two APIs, and they are not the same thing

People searching for "a panel with an API" usually mean one of two different things, and those two cost differently. The first is the inbound API: your reseller customers get a key and send orders to you programmatically, from their own panel or their own code. The second is the outbound API: your panel goes out to a provider, pulls the catalogue, places orders and polls statuses. Whoever is selling you "a panel with an API" usually means only the second one and says nothing about the first.

The difference is practical. The outbound API is what lets you trade at all: without it the catalogue has to be maintained by hand and orders forwarded to the provider manually. The inbound one is what lets you grow on somebody else's effort: a reseller plugged into you with a key brings volume you never had to chase. A panel with only an outbound API caps your turnover at whatever your own marketing brings in.

Our panel runs both, and neither needs custom work. You can connect as many providers as you like, each with your own key, and reseller keys are issued straight from the admin panel, as many as you need.

Comparison

Where people get a panel with an API, and what they actually get

Three usual ways to end up with a panel that has an API. The difference is not whether there is an API, but which of the two you are given.

	Your own script	Child panel	Renting from us
An API for your resellers	Only if you build and debug it	No: you are somebody's reseller	There from day one
Your own provider keys	Yes	No: the catalogue and prices are theirs	As many providers as you want
Compatibility with the standard	As far as you write it	The owner's problem	All seven actions, one to one
Your own domain and brand	Yes	Usually a subdomain of theirs	Your domain or a free address
What you pay for	Licence, server, development	The panel owner's markup	Up to 100 orders a month free

A child panel is the cheapest way to start, but by design it has no reseller API of its own: you are working inside somebody else's panel, with their keys.

What is included

What is already in place for working with resellers

None of this has to be ordered separately or bolted on afterwards - it is how the panel behaves out of the box.

✓All seven actions of the standard: service list, place order, status, refill, refill status, cancel and balance

✓Batch calls of up to 100 orders at a time, so a reseller is not hammering you one order at a time

✓Your own public numbers for services and orders: neither your provider's ids nor their name ever leave your panel

✓Keys issued and revoked from the admin panel, one key per reseller

✓Your own wholesale prices for resellers, separate from the retail prices in your storefront

✓Balances of every connected provider in one place, with a warning before any of them runs dry

✓Your own domain, logo and colours: the reseller sees your brand, not ours

Sharp edges

Worth knowing before you hand out the first key

The batch response shape depends on the action

For order status a batch response comes back as an object keyed by order number, while refill, refill status and cancel return an array of objects. That is not a quirk of ours, it is how the industry standard works, and it trips up half of all hand-written integrations.

Refill status is addressed by the refill number

Creating a refill returns a number of its own, and the status has to be requested by that number, not by the order number. The standard has no "order to its refill" link at all, so the caller is the one who must store it.

Cancellation in the standard is batch-only

A single-order cancel appears in none of the public documentation we surveyed. We accept it too, as a superset - there is no reason to break integrations that already exist - but a reseller should plan for the batch form.

A key is not for everyone who asks

A reseller with a key can burn through your rate limit and your provider balance faster than you will notice. Agree on volumes first and keep separate wholesale prices rather than handing out your storefront rates.

A reseller's turnover is your provider balance

Third-party orders arrive unevenly, and the first thing to run out is not your patience but your purchasing money. An empty provider balance turns a normal queue into stuck orders across the whole panel at once, retail customers included.

Service types differ in the fields they take

An order for followers, one for comments with a custom list and one for a subscription with an interval accept different parameters. The panel knows sixteen types, and the order form and its validation are built from that same registry, so a reseller never has to guess field names.

Compatibility

Why your reseller will not be rewriting their code

The niche has settled on a de facto API standard: one endpoint, POST, the key passed as an ordinary request field, and a JSON response every time. We captured that contract from eleven live panels and checked our own engine against it - actions, parameter names, response shapes and the set of service types. The discrepancies the check turned up have been closed.

In practice that means this: if your reseller has already written an integration against any other panel, connecting to yours is a change of endpoint and key. The reverse is true as well - you are not locking the customer in, and saying so out loud sells better than hiding it.

We do have supersets, but none of them break compatibility: single-order cancel by order number, an alias for placing an order, and one extra field in the service list. Anyone writing strictly to the standard will never notice them.

Who this page is not for. If you are promoting one account or channel of your own, you do not need an API at all - you need services, not a panel. If you have no resellers and do not plan to, the inbound API will sit idle: start with a plain storefront, the keys will still be there later. And if you need non-standard logic inside the API itself - your own fields, your own statuses, your own response format - renting will not give you that: this is the case where you genuinely need your own script and your own developer.

FAQ

Frequently asked questions

What is the difference between a reseller API and a provider API

Direction. A provider API is outbound: your panel reaches out, pulls the catalogue, places orders and polls statuses so that you can trade at all. A reseller API is inbound: other people's orders arrive at your panel using a key you issued. The first is always needed, the second matters once you want to grow on other panels' turnover rather than only your own marketing. Both are built on the same standard, so the same set of calls is used on either side.

Will a reseller have to rewrite their integration for your panel

Not if they wrote it against the industry standard. We checked our API against a contract captured from eleven working panels: the actions, parameter names, response shapes and set of service types all match. Connecting comes down to changing the endpoint and the key. The one thing worth watching is the batch response shape - an object for order status, an array for refill and cancel - and that is a feature of the standard rather than of us.

How much does a panel with an API cost

Orders that go through our own catalogue are not metered at all, at any volume. If you connect third-party providers, the first 100 orders a month are free; beyond that the plan is calculated from actual volume and drops again when volume falls. Orders that reach you from resellers over the API count exactly like your own: there is no separate charge for the inbound API, for the number of keys, or for the number of connected providers.

Try the API on the demo panel

The demo is open without signing up: read the API documentation and see the order form before paying for anything. While orders run through our catalogue the panel is free at any volume.

Start free View demo Message on Telegram