SMM Panel API for Resellers

Using SMM PWR as your provider

The API follows the standard SMM panel API v2 specification. If your panel already talks to other providers, it will talk to us without code changes: point it at the endpoint above, drop in your key and import the service list.

What the API covers

• services returns the full catalogue with prices and order limits
• add places an order from a service ID, a link and a quantity
• status takes one order or up to 100 at once
• refill and cancel work on services that allow them, singly or in batches
• balance returns your remaining balance and currency

Reseller notes

Requests go over HTTPS with your key as a POST parameter. The key lives on your account page and you can regenerate it whenever you want.

Service descriptions

Every service in the services response carries its own description — order limits, refill term and support status. We write them ourselves per service rather than copying a supplier’s marketing text, so what you show your customers is the same thing we show ours.

If your panel runs the standard SMM panel software, tick Copy descriptions when you import our catalogue and each service arrives with its description filled in instead of an empty field.

Services you imported before that option existed do not fill in by themselves. Import them again with the box ticked and the descriptions come across. If you would rather not re-import, paste this small helper into your own admin console — it reads the same public list and fills the descriptions in place. Either way your service IDs, prices and API calls stay exactly as they are.

If you would rather not build anything

A child panel gives you a branded front end on your own domain for $25 per month: your prices, your logo, our catalogue and delivery behind it. You supply the domain and point its nameservers to ours. A child panel sources only from SMM PWR, which is fine if we are your main supplier and limiting if you want several. Order it from your account.

If you do not want to run a panel at all, the affiliate program pays 10% of every top-up your referrals make, with a $10 minimum payout.

One practical warning: refresh the service list on a schedule and diff it. Supplier catalogues change, and a cached list quietly turns into wrong prices and failed orders. There is more on that in our reseller API guide.

Browse the current price list before you integrate.

Code examples

Every call is a POST to the same endpoint carrying your key and an action. The three below place an order and read the reply the safe way; swap the action and parameters for anything in the tables above.

cURL

curl -s https://smmpwr.com/api/v2 \
  -d key=YOUR_API_KEY \
  -d action=add \
  -d service=101 \
  -d link=https://instagram.com/p/EXAMPLE \
  -d quantity=1000

PHP

<?php
$ch = curl_init('https://smmpwr.com/api/v2');
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30,
    CURLOPT_POSTFIELDS     => http_build_query([
        'key'      => 'YOUR_API_KEY',
        'action'   => 'add',
        'service'  => 101,
        'link'     => 'https://instagram.com/p/EXAMPLE',
        'quantity' => 1000,
    ]),
]);
$body = curl_exec($ch);
curl_close($ch);

$res = json_decode($body, true);
if (isset($res['error'])) {          // arrives with HTTP 200 - see below
    throw new RuntimeException($res['error']);
}
echo $res['order'];                  // e.g. 23501

Python

import requests

r = requests.post("https://smmpwr.com/api/v2", timeout=30, data={
    "key": "YOUR_API_KEY",
    "action": "add",
    "service": 101,
    "link": "https://instagram.com/p/EXAMPLE",
    "quantity": 1000,
})

res = r.json()
if "error" in res:                    # arrives with HTTP 200 - see below
    raise RuntimeError(res["error"])
print(res["order"])                   # e.g. 23501

Reading the response

The HTTP status code is not a reliable success signal. A bad key is rejected with 401, but every other failure — unknown service, malformed link, a quantity outside the service limits, an order ID that is not yours — comes back as 200 OK with an error key in the body. Check for that key on every call instead of branching on the status code. This is the single most common reason an integration looks fine and silently drops orders.

A successful add returns nothing but the new order number: {"order": 23501}. A successful status returns charge, start_count, status, remains and currency.

Polling without wasting calls

Two habits keep an integration cheap and fast:

• Ask for orders in batches. status accepts an orders parameter — a comma-separated list of up to 100 IDs in one call. Checking a hundred orders one at a time does the same work a hundred times.
• Cache the service list. services returns the whole catalogue in one response; pull it on a schedule rather than before every order. Prices and limits change when suppliers change them, not between two of your requests.