Skip to content

Developer API: from key to first order

Short version: send a POST request with your key and one action name to the SMMVia endpoint and read the JSON reply. The five action names are balance, services, add, status and cancel.

Last updated

POSThttps://smmvia.com/api/v2

This page is the route from zero to a first tracked order. The field reference lists every parameter and error text, and the code samples walk through each task in a few languages.

What each action is for

Action Use it to Extra fields
balance Read how much money is on your account. none
services Get service IDs, your rate per 1,000, min, max and the cancel flag. none
add Create one order. The price leaves your balance in the same step. service, link, quantity
status Follow one order, or up to 100 in a single request. order or orders
cancel Stop up to 100 unfinished orders and get the undelivered part back on your balance. orders (or order)

Checklist: your first order by API

  1. Step 1: Open an account

    Sign up with an email and a password, then open Account & API. Your key is shown there.

  2. Step 2: Put money on the balance

    Every order is paid from the balance, and the smallest deposit is $5.00. You can call balance and services with zero funds, but add will refuse.

  3. Step 3: Pick a service by its number

    Call services, find the line you want and copy its service number. Names can carry extra tags and may change; the number is what you send.

  4. Step 4: Send a small test

    Call add with service, link and quantity, using a quantity near the minimum. Save the order number that comes back.

  5. Step 5: Watch it to the end

    Ask status every few minutes until the order reaches Completed, Partial, Canceled or Refunded.

Check that order
curl -s https://smmvia.com/api/v2 \
  --data "key=PASTE_YOUR_KEY" \
  --data "action=status" \
  --data "order=80412"
# reply: {"charge":"0.0500","start_count":0,"status":"Pending","remains":500,"currency":"USD"}

Service 205, order 80412 and the amounts above are made up for this page. Use the numbers that your own services list and your own add call return.

Keep the key on your server

The key works like a password for your balance. Keep it in a server-side setting or environment variable, never in browser code, an app or a public repository. Prefer POST: a GET request puts the key into the URL, and URLs end up in logs.

A missing, mistyped or replaced key and a suspended account all get the same reply: Invalid API key. If the key leaked, create a new one on the Account & API page; the old one stops at once.

Reading replies correctly

  • Errors come back as {"error": "text"} with HTTP status 200. Check the body for an error field, not only the status code.
  • Above 300 requests per minute for one key you get HTTP 429. That request did nothing, so sending it again a minute later is harmless.
  • Money values are strings. Rates have 4 decimals; balance and charge may have up to 8, because tiny orders keep their exact amount.
  • The currency field names the unit of every amount. At present it is USD.

How often to ask for status

We refresh order data roughly once a minute, so faster polling only burns your rate limit. Ask every two to five minutes, batch up to 100 IDs per call and drop each order once it is final.

Statuses run Pending, Processing, In progress, then Completed, Partial, Canceled or Refunded. One trap: Canceled with a charge above zero means the money has not come back yet, so treat it as open until charge reads zero. See the status table.

Duplicate orders and retries

The add action has no duplicate protection: the same add sent twice means two orders and two payments. When an add times out or answers Server error, check the Orders page in your account or your balance first, and resend only if no order was created.

The balance, services and status actions change nothing, so you can repeat them freely within the rate limit.

Where the money goes back

If only part of an order is delivered, or you cancel one, the price of the missing part is credited to your SMMVia balance, never to a crypto wallet. The arithmetic is on the refund policy page. Delivery itself also depends on Telegram; our limits page lists what we cannot control.

Prices per 1,000 are in the catalog.

Last verified:

Questions and answers

Can I plug SMMVia into an existing reseller panel?
The request and answer shapes follow the usual "API v2" layout that most SMM panels speak. We checked them with our own cURL, Python, PHP and JavaScript clients, not with every panel script out there. Place one small order through your tool before you route more traffic to us.
How many requests can one key send?
300 per minute, counting every action together. Above that the reply is HTTP 429 with a short JSON error, and nothing is processed for that request.
Will you call my server when an order changes?
No. The API only answers; it never sends callbacks. Ask the status action about up to 100 orders at a time instead.
Is there a refill or drip-feed option in the API?
No. None of our current services offers refill, so the API has no refill action, and the add action does not take drip-feed fields.