GreatSMM API — SMM Panel HTTP API Reference

Base endpoint

POST https://greatsmm.pro/api/v2

Request format

• HTTP method: POST
• Content-Type: application/x-www-form-urlencoded (recommended) or multipart/form-data
• Every request must include your private key and the action parameter
• Rate-limit your cron jobs and back off on errors so the panel stays stable for every reseller

Response format

All responses are JSON. Successful responses return the requested object; failures return an error string. HTTP status is 200 even when the payload contains error — always check the JSON body, not the status code.

Authentication errors

{ "error": "Incorrect API key" }

Never embed your API key in client-side JavaScript. Keep it in server-side environment variables and regenerate it from account settings if it leaks.

• services — list every service available on the panel
• add — create a new order (default, drip-feed, custom comments, subscriptions, mentions, polls, packages)
• status — check the status of a single order
• multi-status — check the status of up to 100 orders in one call
• refill — request a refill on a single completed order
• refill (bulk) — request refill on up to 100 orders at once
• refill_status — check the status of a refill task
• cancel — cancel pending orders (where supported)
• balance — return your current account balance and currency

PHP (cURL)

<?php
$api_url = 'https://greatsmm.pro/api/v2';
$api_key = 'YOUR_API_KEY';

$post = http_build_query([
    'key'      => $api_key,
    'action'   => 'add',
    'service'  => 11,
    'link'     => 'https://instagram.com/p/EXAMPLE/',
    'quantity' => 100,
]);

$ch = curl_init($api_url);
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => $post,
    CURLOPT_SSL_VERIFYPEER => true,
    CURLOPT_TIMEOUT        => 30,
]);

$response = json_decode(curl_exec($ch), true);
curl_close($ch);
print_r($response);

Python (requests)

import requests

API_URL = "https://greatsmm.pro/api/v2"
API_KEY = "YOUR_API_KEY"

payload = {
    "key": API_KEY,
    "action": "add",
    "service": 11,
    "link": "https://instagram.com/p/EXAMPLE/",
    "quantity": 100,
}

response = requests.post(API_URL, data=payload, timeout=30)
print(response.json())

Node.js (axios)

import axios from 'axios';
import qs from 'querystring';

const API_URL = 'https://greatsmm.pro/api/v2';
const API_KEY = process.env.GREATSMM_API_KEY;

const body = qs.stringify({
  key: API_KEY,
  action: 'add',
  service: 11,
  link: 'https://instagram.com/p/EXAMPLE/',
  quantity: 100,
});

const { data } = await axios.post(API_URL, body, {
  headers: { 'Content-Type': 'application/x-www-form-urlencoded' },
  timeout: 30000,
});

console.log(data);

cURL (shell)

curl -X POST "https://greatsmm.pro/api/v2" \
  --data-urlencode "key=YOUR_API_KEY" \
  --data-urlencode "action=add" \
  --data-urlencode "service=11" \
  --data-urlencode "link=https://instagram.com/p/EXAMPLE/" \
  --data-urlencode "quantity=100"

Common error strings returned in the error field:

• Incorrect API key — the key parameter is missing, malformed, or revoked. Regenerate from account settings.
• Incorrect action — the action parameter is missing or not one of the supported method names.
• Incorrect service ID — service was disabled, removed, or you mistyped the ID. Refresh the list with services.
• Not enough funds on balance — top up via Add funds after sign-in.
• Incorrect order ID — order does not exist or belongs to another account.
• Incorrect order status — the order cannot accept the requested action (e.g. canceling an already-completed order).
• Incorrect link — URL fails the service's validator (private profile, deleted post, wrong domain).
• Quantity out of range — quantity is below min or above max for the service.
• Active order with the same link exists — wait for the previous order on this URL to finish or use a different service.

1. Cache services — call it once per hour, not per order. Service IDs are stable; rates and min/max can shift inside that window so a 60-minute cache is the conservative default.
2. Validate ranges client-side — read min and max from the cached service list and reject out-of-range quantities before they hit the API.
3. Poll with multi-status — group up to 100 orders per call instead of one request per order. Saves API quota and finishes a daily reconciliation in seconds.
4. Back off on errors — exponential back-off starting at 2 seconds avoids flooding the panel during supplier outages. Retry only on network errors and 5xx, never on logical error strings.
5. Store both charge and currency — the panel may run in a different base currency than the user; storing both fields prevents reconciliation drift.
6. Use refill buttons strategically — refills are free but suppliers prioritise new orders. Schedule refill polling in off-peak windows.
7. Never embed the API key in client JS — keep it server-side. Public-facing apps should proxy through your own backend, which holds the secret.

Pair these automation docs with the public catalog (service IDs and rates) and the plain-language guides on the FAQ. Commercial scope and refill terms sit in the Terms of Service. Refund handling is on the Refund Policy page. Data handling and your statutory rights are in the Privacy Policy.