Skip to content
SocialBooster
fr en
Log In Sign up

The SocialBooster API

Build your own panel, bot or reseller site on top of SocialBooster. Read your balance, place orders and follow their progress with plain HTTPS and JSON. The prices the API shows are your own.

Last updated: October 19, 2026

JSON over HTTPS
REST
Secret key
Bearer
Whole amounts
FCFA

Base URL

https://social-booster.online/api/v1

Quick start

Every request goes to the base URL above, over HTTPS, with your key in the Authorization header.

  1. Sign in, open API keys in your account and create a key. Copy it: it is shown only once.
  2. Top up your balance. API orders are paid from it, exactly as on the website.
  3. Call GET /services to choose a service, then POST /orders to place an order.

Create an account

Authentication

Send your key as a bearer token in the Authorization header of every request. A key is sbk_ followed by 40 letters and digits.

Authorization: Bearer sbk_your_key
Keep your key on your server. Never put it in a mobile app, a web page or a public repository: whoever holds it can spend your balance. The API sends no CORS headers, so a browser cannot call it with your key. That is on purpose.

The key goes in the header only: a key in the address is ignored. If you lose a key or suspect a leak, revoke it on the API keys page and create another. You may hold up to 5 active keys at once, which lets you replace one without a break.

A missing, malformed or revoked key gets 401 invalid_api_key. If API access was switched off for your account you get 403 api_access_disabled.

Conventions

  • Everything is JSON in UTF-8. Send Content-Type: application/json with the body of a POST (a form-encoded body works too).
  • A success is {"data": …}. A list adds {"meta": …}. A failure is {"error": …} (see Errors).
  • Amounts are whole numbers of FCFA. There are no decimals anywhere.
  • Dates are ISO 8601 in UTC, for example 2026-10-18T09:30:00Z.
  • Messages are in English. In your program, rely on the code of an error, never on its message.
  • Every response carries an X-Request-Id header, repeated as request_id in errors. Quote it if you contact support.

Balance

GET /balance

Returns what you can still spend.

Request
curl https://social-booster.online/api/v1/balance \
  -H "Authorization: Bearer sbk_your_key"
Response
{
  "data": {
    "balance": 12500,
    "currency": "FCFA"
  }
}

List services

GET /services

Returns every service you can order, with the price you pay for it: special prices and discounts are already applied, you never see the public price here.

  • id string

    The identifier to send as service when ordering. It does not change.

  • network string

    The network: TikTok, Instagram…

  • category string

    The group of the service inside the network: Followers, Likes…

  • type string

    What an order carries besides the link. standard: a quantity. custom_comments: your own comments (comments). mentions_custom_list: a list of usernames to mention (usernames). For the last two, the quantity is the number of lines in the list.

  • name string

    The name of the service.

  • price_per_1000 integer

    Your price, in FCFA, for 1,000 units.

  • min_quantity integer

    The smallest quantity you may order.

  • max_quantity integer

    The largest quantity you may order.

Field Type Meaning
id string The identifier to send as service when ordering. It does not change.
network string The network: TikTok, Instagram…
category string The group of the service inside the network: Followers, Likes…
type string What an order carries besides the link. standard: a quantity. custom_comments: your own comments (comments). mentions_custom_list: a list of usernames to mention (usernames). For the last two, the quantity is the number of lines in the list.
name string The name of the service.
price_per_1000 integer Your price, in FCFA, for 1,000 units.
min_quantity integer The smallest quantity you may order.
max_quantity integer The largest quantity you may order.
Request
curl https://social-booster.online/api/v1/services \
  -H "Authorization: Bearer sbk_your_key"
Response
{
  "data": [
    {
      "id": "tiktok-followers-africa",
      "network": "TikTok",
      "category": "Followers",
      "type": "standard",
      "name": "Followers Africa",
      "price_per_1000": 2500,
      "min_quantity": 100,
      "max_quantity": 50000
    }
  ]
}

Place an order

POST /orders

Charges your balance and sends the order to be delivered. The rules are those of the order form on the website.

  • service string, required

    The id of a service, from GET /services.

  • link string, required

    The address of the profile, page or post to boost: http or https, 500 characters at most. It must stay public until delivery is complete.

  • quantity integer

    Required for a standard service: between the min_quantity and the max_quantity of the service, both included. Optional for a service that takes a list: if you send it, it must equal the number of lines in the list.

  • comments string

    Required for a custom_comments service, refused for the others: your comments, one per line (lines separated by \n). Empty lines are ignored. Their number must be between the min_quantity and the max_quantity of the service, and each comment is 1,000 characters at most.

  • usernames string

    Required for a mentions_custom_list service, refused for the others: the usernames to mention, one per line (lines separated by \n), 100 characters at most each. Their number is bounded as for comments.

Field Type Meaning
service string, required The id of a service, from GET /services.
link string, required The address of the profile, page or post to boost: http or https, 500 characters at most. It must stay public until delivery is complete.
quantity integer Required for a standard service: between the min_quantity and the max_quantity of the service, both included. Optional for a service that takes a list: if you send it, it must equal the number of lines in the list.
comments string Required for a custom_comments service, refused for the others: your comments, one per line (lines separated by \n). Empty lines are ignored. Their number must be between the min_quantity and the max_quantity of the service, and each comment is 1,000 characters at most.
usernames string Required for a mentions_custom_list service, refused for the others: the usernames to mention, one per line (lines separated by \n), 100 characters at most each. Their number is bounded as for comments.

Also send an Idempotency-Key header, so that a retry can never order twice. See Safe retries below.

Answers

  • 201 —

    Order placed. Its status is processing, or failed if the order could not be started: you were then refunded in full (see charge and refunded).

  • 200 —

    Replay: this Idempotency-Key already placed an order. That order is returned, with the header Idempotent-Replayed: true, and nothing is charged again.

  • 402 insufficient_balance

    Your balance is too low. The error carries balance and required. Nothing was recorded.

  • 409 idempotency_key_reused

    The key was used for a different order (another service, link, quantity or list).

  • 422 validation_failed

    A field is wrong. error.errors lists the messages by field.

  • 429 too_many_requests

    You are over a limit: see Rate limits.

Status Code Meaning
201 — Order placed. Its status is processing, or failed if the order could not be started: you were then refunded in full (see charge and refunded).
200 — Replay: this Idempotency-Key already placed an order. That order is returned, with the header Idempotent-Replayed: true, and nothing is charged again.
402 insufficient_balance Your balance is too low. The error carries balance and required. Nothing was recorded.
409 idempotency_key_reused The key was used for a different order (another service, link, quantity or list).
422 validation_failed A field is wrong. error.errors lists the messages by field.
429 too_many_requests You are over a limit: see Rate limits.
Request
curl https://social-booster.online/api/v1/orders \
  -H "Authorization: Bearer sbk_your_key" \
  -H "Idempotency-Key: shop-order-48213" \
  -H "Content-Type: application/json" \
  -d '{"service": "tiktok-followers-africa", "link": "https://www.tiktok.com/@awa", "quantity": 1000}'
Example: a service that takes comments, 3 lines = quantity 3
curl https://social-booster.online/api/v1/orders \
  -H "Authorization: Bearer sbk_your_key" \
  -H "Idempotency-Key: shop-order-48214" \
  -H "Content-Type: application/json" \
  -d '{"service": "facebook-custom-comments", "link": "https://www.facebook.com/awa/posts/123", "comments": "Magnifique !\nBravo pour cette publication\nMerci du partage"}'
Response 201
{
  "data": {
    "id": 1207,
    "service": "tiktok-followers-africa",
    "service_name": "Followers Africa",
    "link": "https://www.tiktok.com/@awa",
    "quantity": 1000,
    "price_per_1000": 2500,
    "charge": 2500,
    "refunded": 0,
    "status": "processing",
    "start_count": null,
    "remains": null,
    "created_at": "2026-10-18T09:30:00Z"
  }
}
Response 402
{
  "error": {
    "code": "insufficient_balance",
    "message": "The balance is too low for this order.",
    "balance": 1000,
    "required": 2500,
    "request_id": "0b8f2f3e-2a0e-4d5b-8f0a-6b6f2c1d9a10"
  }
}
Response 422
{
  "error": {
    "code": "validation_failed",
    "message": "The given data was invalid.",
    "errors": {
      "quantity": ["The quantity must be between 100 and 50,000."]
    },
    "request_id": "7c1d0e5a-93b4-4f6e-a2b8-5d41c6f0e9a3"
  }
}

How the price is computed

The order costs quantity × price_per_1000 ÷ 1,000, rounded to the nearest FCFA (a half rounds up) and never less than 1 FCFA.

  • 1,500 units at 2,750 FCFA per 1,000 cost 4,125 FCFA.
  • 333 units at 1,500 FCFA per 1,000 come to 499.5 and cost 500 FCFA.

The price is fixed the moment the order is placed: changing your prices later never changes an order already made.

List orders

GET /orders

Returns your orders, newest first. The orders of other members never appear.

  • status string

    Only the orders in this status: pending, processing, completed, partial or failed.

  • ids string

    Only these orders: order numbers separated by commas, at most 100.

  • per_page integer

    Orders per page, from 1 to 100 (25 by default).

  • cursor string

    The meta.next_cursor of the previous page, to get the page after it.

Parameter Type Meaning
status string Only the orders in this status: pending, processing, completed, partial or failed.
ids string Only these orders: order numbers separated by commas, at most 100.
per_page integer Orders per page, from 1 to 100 (25 by default).
cursor string The meta.next_cursor of the previous page, to get the page after it.
Request
curl "https://social-booster.online/api/v1/orders?status=processing&per_page=1" \
  -H "Authorization: Bearer sbk_your_key"
Response
{
  "data": [
    {
      "id": 1207,
      "service": "tiktok-followers-africa",
      "service_name": "Followers Africa",
      "link": "https://www.tiktok.com/@awa",
      "quantity": 1000,
      "price_per_1000": 2500,
      "charge": 2500,
      "refunded": 0,
      "status": "processing",
      "start_count": 3572,
      "remains": 157,
      "created_at": "2026-10-18T09:30:00Z"
    }
  ],
  "meta": {
    "per_page": 1,
    "next_cursor": "1207"
  }
}

When meta.next_cursor is null, there is no page after this one. Treat the cursor as opaque: pass it back as it came.

Several orders in one call
curl "https://social-booster.online/api/v1/orders?ids=1207,1206,1205" \
  -H "Authorization: Bearer sbk_your_key"

To follow many orders, ask for them together with ids: one call instead of one per order. Poll sparingly: a status changes over minutes or hours, not seconds.

Get an order

GET /orders/{id}

Returns one order. An order that is not yours answers 404 not_found, exactly like an order that does not exist.

Request
curl https://social-booster.online/api/v1/orders/1207 \
  -H "Authorization: Bearer sbk_your_key"

The order

  • id integer

    The order number.

  • service string

    The id of the service.

  • service_name string

    The name of the service when the order was placed.

  • link string

    The address the order is for.

  • quantity integer

    The quantity ordered.

  • price_per_1000 integer

    The price per 1,000 units that applied to this order.

  • charge integer

    What the order cost, in FCFA.

  • refunded integer

    What was given back to your balance, in FCFA: 0 unless the order failed or was partly delivered.

  • status string

    See Order statuses.

  • start_count integer or null

    The count on the profile when delivery began, once it is known.

  • remains integer or null

    The quantity not delivered yet, once it is known.

  • created_at string

    When the order was placed, ISO 8601 in UTC.

Field Type Meaning
id integer The order number.
service string The id of the service.
service_name string The name of the service when the order was placed.
link string The address the order is for.
quantity integer The quantity ordered.
price_per_1000 integer The price per 1,000 units that applied to this order.
charge integer What the order cost, in FCFA.
refunded integer What was given back to your balance, in FCFA: 0 unless the order failed or was partly delivered.
status string See Order statuses.
start_count integer or null The count on the profile when delivery began, once it is known.
remains integer or null The quantity not delivered yet, once it is known.
created_at string When the order was placed, ISO 8601 in UTC.

Order statuses

An order goes from pending to processing, then ends in one of three final statuses.

  • pending

    Recorded and about to be sent.

  • processing

    Accepted and being delivered. An order waiting for a check on our side also reads processing.

  • completed

    Fully delivered. Final.

  • partial

    Partly delivered: the part that was not delivered was refunded (see refunded). Final.

  • failed

    Not delivered: refunded in full. Final.

Status Meaning
pending Recorded and about to be sent.
processing Accepted and being delivered. An order waiting for a check on our side also reads processing.
completed Fully delivered. Final.
partial Partly delivered: the part that was not delivered was refunded (see refunded). Final.
failed Not delivered: refunded in full. Final.

Once an order is completed, partial or failed, it never changes again: you can stop following it.

Safe retries

A network can fail after we received your request but before you got the answer. Retrying blindly could order twice and charge you twice. To make a retry safe, send an Idempotency-Key header with POST /orders: any string of up to 255 characters that is unique to the order, for example its number in your own system, or a UUID.

  • The first call with a key places the order (201). The same key again returns that very order (200, Idempotent-Replayed: true): no second order and no second charge, even if your balance has changed since.
  • Reusing a key for a different order is refused (409), so a mistake in your code cannot pass for a success.
  • Keys are yours alone: another account may use the same string.
  • Without the header, every call places a new order.
  • When you get no answer, or a 5xx, the outcome is unknown: send the same call again with the same key.

Errors

A failed request answers with an HTTP status and a JSON body, {"error": {"code": …, "message": …, "request_id": …}}, plus the fields specific to the error. Test the code, never the message.

  • invalid_api_key 401

    The key is missing, malformed, unknown or revoked.

  • insufficient_balance 402

    Your balance is too low. Carries balance and required.

  • api_access_disabled 403

    API access is switched off for your account.

  • not_found 404

    No such address, or an order that is not yours.

  • method_not_allowed 405

    Wrong HTTP method for this address; the Allow header lists the right ones.

  • idempotency_key_reused 409

    The key was used for a different order.

  • validation_failed 422

    Carries errors, the messages by field.

  • too_many_requests 429

    Carries retry_after, in seconds.

  • server_error 500

    Something went wrong on our side. Retry later, and quote the request_id if it persists.

  • service_unavailable 503

    Maintenance, or the API is switched off. Retry later.

  • http_error other

    Any other HTTP error, for example 413 when a request is too large.

Code Status Meaning
invalid_api_key 401 The key is missing, malformed, unknown or revoked.
insufficient_balance 402 Your balance is too low. Carries balance and required.
api_access_disabled 403 API access is switched off for your account.
not_found 404 No such address, or an order that is not yours.
method_not_allowed 405 Wrong HTTP method for this address; the Allow header lists the right ones.
idempotency_key_reused 409 The key was used for a different order.
validation_failed 422 Carries errors, the messages by field.
too_many_requests 429 Carries retry_after, in seconds.
server_error 500 Something went wrong on our side. Retry later, and quote the request_id if it persists.
service_unavailable 503 Maintenance, or the API is switched off. Retry later.
http_error other Any other HTTP error, for example 413 when a request is too large.

Rate limits

  • 120 requests per minute per account, whichever of your keys sent them: creating more keys does not raise the limit.
  • Placing orders: 30 per minute and 600 per hour per account.
  • Requests carrying an unknown or revoked key: 30 per minute per IP address, after which that address is turned away until the minute is over.

Over a limit you get 429 too_many_requests with a Retry-After header, in seconds. Wait that long and retry; do not retry in a loop.

Examples

The same flow in two languages: read the services, place an order safely, check on it later. cURL examples are given with each endpoint above.

PHP
<?php

$base = 'https://social-booster.online/api/v1';
$key = getenv('SOCIALBOOSTER_KEY'); // read it from the environment, never write it in the code

function call(string $method, string $path, ?array $body = null, array $headers = []): array
{
    global $base, $key;

    $curl = curl_init($base.$path);
    curl_setopt_array($curl, [
        CURLOPT_CUSTOMREQUEST => $method,
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_TIMEOUT => 60,
        CURLOPT_HTTPHEADER => array_merge([
            'Authorization: Bearer '.$key,
            'Accept: application/json',
            'Content-Type: application/json',
        ], $headers),
        CURLOPT_POSTFIELDS => $body === null ? null : json_encode($body),
    ]);

    $text = curl_exec($curl);
    $status = curl_getinfo($curl, CURLINFO_RESPONSE_CODE); // 0 when there was no answer at all

    return [$status, json_decode((string) $text, true)];
}

// 1. Read the services you may order, and what you pay for each.
[, $services] = call('GET', '/services');

// 2. Place an order. Keep the Idempotency-Key with the order in your own database:
//    if anything fails on the way, send the very same call again with the very same key.
[$status, $reply] = call('POST', '/orders', [
    'service' => 'tiktok-followers-africa',
    'link' => 'https://www.tiktok.com/@awa',
    'quantity' => 1000,
], ['Idempotency-Key: shop-order-48213']);

if ($status === 201 || $status === 200) {
    $order = $reply['data'];
} elseif ($status === 402) {
    // Not enough balance: $reply['error']['required'] FCFA are needed. Top up, then place the order again.
} elseif ($status === 0 || $status >= 500) {
    // The outcome is unknown: do not place a new order, retry the same call with the same key.
}

// 3. Check on it later.
[, $reply] = call('GET', '/orders/'.$order['id']);
echo $reply['data']['status'];
Node.js
const base = 'https://social-booster.online/api/v1';
const key = process.env.SOCIALBOOSTER_KEY; // read it from the environment, never write it in the code

async function call(method, path, body, headers = {}) {
  const response = await fetch(base + path, {
    method,
    headers: {
      Authorization: `Bearer ${key}`,
      Accept: 'application/json',
      'Content-Type': 'application/json',
      ...headers,
    },
    body: body ? JSON.stringify(body) : undefined,
    signal: AbortSignal.timeout(60_000),
  });

  return { status: response.status, body: await response.json() };
}

// 1. Read the services you may order, and what you pay for each.
const services = (await call('GET', '/services')).body.data;

// 2. Place an order. Keep the Idempotency-Key with the order in your own database:
//    if anything fails on the way, send the very same call again with the very same key.
let order;

try {
  const { status, body } = await call('POST', '/orders', {
    service: 'tiktok-followers-africa',
    link: 'https://www.tiktok.com/@awa',
    quantity: 1000,
  }, { 'Idempotency-Key': 'shop-order-48213' });

  if (status === 201 || status === 200) {
    order = body.data;
  } else if (status === 402) {
    // Not enough balance: body.error.required FCFA are needed. Top up, then place the order again.
  } else if (status >= 500) {
    // The outcome is unknown: retry the same call with the same key.
  }
} catch {
  // No answer (network, timeout): the outcome is unknown. Retry the same call with the same key.
}

// 3. Check on it later.
console.log((await call('GET', `/orders/${order.id}`)).body.data.status);

Good practice

  • Call the API from your server only, and keep the key in the environment, not in your code.
  • Always send an Idempotency-Key, and store it with the order in your own database so that a retry reuses it.
  • Read prices from GET /services instead of writing them in your code, and compare charge with what you expected.
  • Answer a 402 by topping up, not by retrying.
  • Treat timeouts and 5xx as unknown outcomes: retry the same call with the same key.
  • Revoke a key the moment you suspect it leaked.

Help

A question, special prices for your volume, or a higher limit? Write to support@social-booster.online.