SMMScoutindependent panel directory

Home / Guides / SMM panel API integration

How to integrate an SMM panel API

Every SMM panel API is the same four calls around a base endpoint: service list, balance, order placement, and order status. Learn the shape once and every panel in the directory works the same way.

Reviewed by the SMMScout data team · updated 2026-08-14 · measured against the API tester on this site and dated directory data · methodology · editorial policy · disclosure

Key facts

Endpoint
One base URL (e.g. /api/v1) plus an action parameter; keys are per-account.
Calls
services, balance, add, status: everything else is convenience.
Response
JSON with a numeric status code; 100 is the universal success value.
First rule
Test with services and a small order before funding a big balance.

The request shape

The classic format is a single endpoint with named parameters. A typical service-list call looks like this:

POST /api/v1
  api_key: your-key
  action: services

→ JSON: { status: 100, data: [ { service: 1234, name: "Followers",
    rate: 2.5, min: 10, max: 100000, category: "Instagram" } ] }

Order placement sends the same base with action=add, service, link and quantity, and returns an order ID. Status polling sends action=status with that ID. Some panels use GET, some POST, but the parameters are the same.

The four calls

  1. services: pull the manifest, cache it, reprice from it. This is read-only and safe to call often.
  2. balance: confirm prepaid credit before every order batch; most panels reject with a numeric error when balance is low.
  3. add: place the order with service, link and quantity; store the order ID immediately, because it is your only handle.
  4. status: poll until the terminal state; handle pending, in-progress and refill states explicitly.

Order states and refills

Orders typically move through pending (queued), in-progress (delivering), completed, and occasionally partial or canceled. Refills show up as a separate state or a new order ID: build your client UI around the state machine, not around one poll. The directory records per-panel latency and refill terms so you can compare before integrating a provider.

Never put API keys in URLs, logs or client-side code. Keys are credentials: treat them like passwords, rotate them on suspicion, and scope them to read-only where the panel supports it.

Hardening

  • Retry timeouts with backoff, but never retry order placement without deduplication: a double-click can mean a double order.
  • Validate every response against the documented shape before trusting fields.
  • Keep the manifest cache fresh (daily) so prices and min/max never go stale.
  • Monitor response time per provider; the directory records measured latency for comparison.

Generate real calls

The API tester generates working requests for services, balance, orders and status from any endpoint and key, and shows the exact response shape. Start there before writing any code.

FAQ

Frequently asked questions

What is the standard SMM panel API format?

Nearly all panels implement the classic service-format: POST or GET with an action parameter (services, balance, add, status), an API key, and named fields like service, link and quantity. Responses are JSON, often with numeric status codes (100 = success).

Do I need to code to use a panel API?

To call it by hand, no: the API tester on this site generates a working request from an endpoint and key. To integrate for reselling, you need a few hours of scripting that polls services, places orders and parses responses.

How do I test a provider API before paying?

Call services first (read-only, no balance risk), verify the response shape against the documented format, then run one small order per service tier and check status transitions over a day. The directory records each panel's measured latency.

What is the difference between a panel API and a service API?

A service API (like the one your social tool vendors expose) is per-product; a panel API is the wholesale interface: service list, balance, order placement and status. Resellers integrate the panel API and repackage it.

Why does my order stay "pending" forever?

Pending usually means the provider queues before delivery. If it never moves, check your quantity against the min/max range, confirm the link format, and verify the service accepts your target platform at all.