How the SMM panel API works

Almost every SMM panel exposes the same simple API, inherited from the panel software most of them run. It is how resellers connect to providers and how scripts place orders.

One endpoint, one key, an action

Requests are HTTP POSTs to a single address, typically /api/v2 on the panel's domain, with form fields. The key field carries the account's API key; the action field says what to do. Answers are JSON.

curl -X POST https://examplepanel.com/api/v2 \
  -d key=YOUR_KEY -d action=services

The common actions

• services: the catalog. An array of objects with service (ID), name, category, type, rate (price per 1,000 in the account's currency), min, max, and flags such as refill, cancel and dripfeed.
• add: places an order with service, link and quantity; drip-feed orders add runs and interval, custom comments a comments list. Returns an order ID.
• status: an order's status, charge, start_count and remains; several orders can be queried at once.
• refill and cancel: request a refill or cancellation where the service allows it.
• balance: the account's balance and currency.

Details that trip people up

• Rates are per 1,000 units, except for services of type "Package", whose rate is the price of the whole package.
• Prices are in the account's currency, which is not always US dollars.
• Numbers arrive as strings or numbers depending on the panel; names often arrive HTML-escaped.
• An API key can spend the account's balance. Keep it private and never paste it into a public page or tool.

IntelSMM reads catalogs only, never places orders, and stores any key it is given encrypted. How the crawler behaves.