Developers
The API: order from your own software
Place orders, check statuses, read your balance and the tool list programmatically. Every request is a POST to one endpoint with your key, every response is JSON. Below are recipes for the actions you’ll actually use.
Setup
Key, endpoint, format
Key
Your API key is on the API page in your account. Pass it as the key parameter on every request.
Endpoint
One URL: https://smmpanelus.com/api/v2. Method is POST. The exact address is also shown on the API page.
Format
The action is chosen with the action parameter; the response is always JSON. The service field is the tool ID.
Recipes
The requests you’ll use
New order
A tool ID (service), a public link, and a quantity. You get back the order number.
Request
POST https://smmpanelus.com/api/v2
key = YOUR_API_KEY
action = add
service = 1024
link = https://your-network.com/your-post
quantity = 1000Response
{ "order": 23501 }Order with gradual delivery
Add runs and interval (minutes) to spread delivery — where the tool supports it.
Request
POST https://smmpanelus.com/api/v2
key = YOUR_API_KEY
action = add
service = 1024
link = https://your-network.com/your-post
quantity = 1000
runs = 5
interval = 30Response
{ "order": 23502 }Order status
Pass the order number — get the status, start count, charge, and what remains.
Request
key=YOUR_API_KEY&action=status&order=23501
Response
{
"charge": "0.90",
"start_count": "1200",
"status": "In progress",
"remains": "300",
"currency": "USD"
}Several orders at once
Pass comma-separated numbers in orders — up to 100 at a time.
Request
key=YOUR_API_KEY&action=status&orders=23501,23502,23503
Response
{
"23501": { "status": "Completed", "remains": "0" },
"23502": { "status": "Partial", "remains": "150" },
"23503": { "error": "Incorrect order ID" }
}Tool list
The full catalog with IDs, limits and options. Cache it — it changes less often than orders.
Request
key=YOUR_API_KEY&action=services
Response
[
{
"service": 1024,
"name": "…",
"type": "Default",
"category": "…",
"min": "50",
"max": "100000",
"refill": true,
"cancel": true
}
]Balance
Your current balance and account currency.
Request
key=YOUR_API_KEY&action=balance
Response
{ "balance": "100.84", "currency": "USD" }Refill
Request a top-up — where the tool offers it. Check it with a second action.
Request
key=YOUR_API_KEY&action=refill&order=23501 key=YOUR_API_KEY&action=refill_status&refill=901
Response
{ "refill": "901" }
{ "status": "Completed" }Some tools take extra parameters (for example comments or username) — the exact fields are on the tool and on the API page.
Responses & errors
Read the error field
A successful response carries the action’s data; on a problem you get an object with an error field. Check it before trusting the rest.
# error example { "error": "Incorrect service ID" }
Good practice
A few habits
Keep your key like a password. Don’t commit it to a public repo; regenerate it if exposed. Security.
Cache the tool list. It changes less often than orders — don’t fetch it on every request.
Check error first. Look for the error field before parsing the useful data.
Steady pace, HTTPS. Don’t send requests faster than you need, and always call over HTTPS.
FAQ
Common questions
Where’s my API key?
key parameter and keep it private.What’s the endpoint?
https://smmpanelus.com/api/v2 with method POST. The exact address is also shown on the API page.Why is the field named service, not tool?
service is the API field name kept for compatibility; it’s the platform’s tool ID. We don’t change the backend.How do I order in volume?
add per order and check up to 100 statuses at once with orders. Without code, mass order is handy.Is there a request limit?
What about a Partial result over the API?
Next: security · glossary · order statuses.
The API, in detail
Building on the SmmPanelUS API
The SmmPanelUS API lets you place orders, check their status, list tools, and read your balance from your own software, so you can run volume work without touching the dashboard. Every request is a POST to a single endpoint, authenticated with your API key, and every response comes back as JSON. If you’ve used a standard API of this kind before, this will feel familiar; if not, the recipes above cover the handful of actions you’ll actually use.
The key and the endpoint
Your API key lives on the API page of your account, and you pass it as the key parameter on every request. The endpoint is a single URL on smmpanelus.com, and the action you want is chosen with the action parameter: add to place an order, status to check one, services to list tools, balance to read your balance, and refill where a tool supports it. Note that the field naming an item is service in the API; this is the platform’s tool ID. The field name is kept for compatibility even though the platform calls these tools.
Placing and checking orders
To place an order you send add with a tool ID, a public link, and a quantity, and you get back the new order number. To check it, send status with that order number and read the status, the start count, the amount charged, and what remains. You can check several orders at once by passing a comma-separated list. Orders move through the same statuses you’d see in the dashboard, so a Partial or Canceled result over the API behaves exactly as it does in the account, with the unused amount returning to your balance.
Good practices
Treat your API key like a password: keep it private, don’t commit it to a public repository, and regenerate it if it’s ever exposed. Cache the tool list rather than fetching it on every order, since it changes far less often than your orders do. Handle errors by checking for an error field in the response before trusting the rest, and don’t send requests faster than you need to — a steady, reasonable pace keeps everything reliable. Always call the endpoint over HTTPS.
Any language that can POST
Because the API is plain HTTP with form parameters and JSON responses, you can call it from any language that can make a POST request — there’s no SDK to install and nothing framework-specific. A few lines in your language of choice are enough to place an order and read the result, which makes it easy to drop into an existing workflow, a scheduled job, or a small script. If you’re wiring it into something larger, keep the order numbers you receive so you can check status later, and store them alongside whatever they map to on your side. That single habit — remembering the order number the add call returns — is what turns a one-off request into a system you can rely on.
Keep your key safe with the security guide, and the full field reference is on the API page in your account. If a term is unfamiliar, the glossary explains it, and order statuses describe what each status response means.
Grab your key and start
Create an account — your API key appears on the API page in your account.