SMM Panel API v2 Integration Guide: Actions, Examples, Errors

The SpotBoost reseller API lets you place and manage orders from your own panel, app or scripts. It follows the widely used SMM panel API v2 style, so if you have integrated another panel before, most of this will feel familiar. This guide covers authentication, every action, example requests with curl, and the error handling that separates a fragile integration from a reliable one.

The official reference, including the exact parameter list for each action and example responses, is on the API documentation page. Treat it as the source of truth; this article explains how to use it well.

The basics

Endpoint: https://spotboost.top/api/v2
Method: POST
Authentication: your API key, sent as the key parameter with every request
Operation: chosen with the action parameter
Response format: JSON

Your API key is on the Account page after you create a free account. Keep it on your server only. Never put it in browser JavaScript, mobile app bundles or public repositories. If you think it has leaked, generate a new one from the Account page.

Available actions

Action	What it does
services	Returns the service list with IDs, names, rates and limits
add	Places a new order
status	Returns the status of one or more orders
refill	Requests a refill on an eligible order
refill_status	Returns the status of a refill request
cancel	Requests cancellation of eligible orders
balance	Returns your current balance and currency

Example requests

The examples below use curl with form-encoded parameters. Replace YOUR_API_KEY, SERVICE_ID, ORDER_ID and the link with your own values. Parameter names other than key and action follow the common v2 convention; confirm them against the API docs before going live.

Check your balance

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=balance

The response contains your balance and its currency. This is the simplest request to confirm that your key and connection work.

Fetch the service list

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=services

The response is a list of services. Each entry includes the service ID you will use when ordering, along with its name, category, rate per 1,000, minimum and maximum quantity, and flags for features such as refill and cancel. Cache this list and refresh it on a schedule, for example every few hours, rather than calling it before every order.

Place an order

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=add -d service=SERVICE_ID -d link=https://open.spotify.com/track/TRACK_ID -d quantity=1000

A successful response returns the new order ID. Store it immediately; you need it for status, refill and cancel. Some services accept extra fields, such as keywords for Search source plays, and the docs list those per service type.

Place a drip-feed order

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=add -d service=SERVICE_ID -d link=https://open.spotify.com/track/TRACK_ID -d quantity=500 -d runs=10 -d interval=1440

Drip-feed splits the order into runs at an interval. The interval is expressed in minutes and quantity is the amount delivered in each run, so the total is quantity multiplied by runs. Services that need extra input, such as an editorial playlist, search keywords or a target country, take it in the groups parameter (one entry per line). Drip-feed is the recommended way to keep campaigns gradual and in line with an artist's organic engagement.

Check order status

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=status -d order=ORDER_ID

The response includes the order status, the charge, the start count and how many units remain. Many v2 APIs also accept several order IDs in one request, separated by commas; see the docs for the parameter name and limit.

Request a refill and check it

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=refill -d order=ORDER_ID

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=refill_status -d refill=REFILL_ID

The refill action returns a refill ID when accepted. Use refill_status with that ID to follow its progress. Refills only work on services that offer them and within the refill period.

Cancel an order

curl -X POST https://spotboost.top/api/v2 -d key=YOUR_API_KEY -d action=cancel -d orders=ORDER_ID

Cancel only works on services that support it. Undelivered parts of canceled or partial orders go back to your balance automatically.

Understanding order statuses

Order statuses follow the usual SMM panel lifecycle. Your integration should handle at least these states:

Pending: accepted, not yet started.
In progress / processing: delivery is running.
Completed: fully delivered.
Partial: delivery stopped before the full quantity; the undelivered part is returned to your balance.
Canceled: the order was canceled; the undelivered amount is returned.

Map these to your own client-facing statuses, and when you see partial or canceled, refund your client for the undelivered part automatically.

Error handling

When a request cannot be processed, the API returns a JSON response describing the error instead of the normal result. Always check for an error before reading other fields. Common causes:

Invalid or missing key. Check that the key is sent as a POST parameter and has not been regenerated.
Unknown action or service. Refresh your cached service list; services can be added, changed or removed.
Quantity out of range. Validate against the minimum and maximum from the services action before sending.
Invalid link. Only full open.spotify.com links are accepted for Spotify services; spotify.link short links are rejected. See Spotify link formats explained.
Insufficient balance. Check balance before large batches, and top up in advance.
Not eligible for refill or cancel. Check the service flags and the order's state first.

Reliability checklist

Store the API key server-side in an environment variable or secrets store.
Validate links, link types and quantities before calling add.
Save the order ID from every successful add response right away.
Never retry an add request blindly after a timeout; first check whether an order was created, to avoid duplicates.
Poll status at a sensible interval, such as every few minutes, and batch order IDs where the API allows it.
Log every request and response, with the key removed, for debugging.
Refresh the services list on a schedule and alert yourself when a mapped service disappears or its rate changes.
Handle partial and canceled states with automatic client refunds.

Rate of requests

Be considerate with request volume. Batch status checks where possible, avoid calling the services action on every page load, and space out bulk order submissions rather than firing hundreds of requests at once. A calm, predictable request pattern is easier to debug and less likely to run into limits.

Going live

Before you connect real clients, run small test orders for each service type you plan to offer, and walk through status, refill and cancel. If you are reselling, the guide to reselling Spotify services covers pricing and client communication. Stuck on something? Open a ticket or email support@spotboost.top with the request you sent (without your key) and the response you received.

Key takeaways

All requests are POST to https://spotboost.top/api/v2 with key and action; responses are JSON.
Seven actions cover the full lifecycle: services, add, status, refill, refill_status, cancel and balance.
Confirm exact parameter names on the /api page, and cache the service list.
Check every response for errors, avoid duplicate orders on retries and handle partial and canceled states.
Use drip-feed through the API to keep campaigns gradual and proportionate.