Social Booster API documentation

Overview

API v2 uses HTTPS POST requests to https://www.socialbooster.net.ng/api/v2. Requests and responses use JSON. Form-encoded requests are also accepted for compatibility with standard reseller panels. API orders use the authenticated customer wallet and the current customer rate.

Authentication

Create an API key from the signed-in API dashboard. Send it in the Authorization header. Keys are shown once, must be stored securely and should never be placed in browser-side JavaScript or a public repository.

Authorization: Bearer sb_live_YOUR_API_KEY

Each key is limited to 120 requests per minute. Revoke a key immediately if it is exposed.

Available actions

Examples

List services

curl -X POST https://www.socialbooster.net.ng/api/v2 \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action":"services"}'

Place an order

curl -X POST https://www.socialbooster.net.ng/api/v2 \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action":"add",
    "service":"SERVICE_ID",
    "link":"https://example.com/your-public-target",
    "quantity":1000,
    "idempotency_key":"your-unique-order-001"
  }'

Check an order

{
  "action": "status",
  "order": "YOUR_ORDER_REFERENCE"
}

Responses and errors

Successful requests return JSON with the requested data. Error responses include a stable machine-readable code and a safe message. Common HTTP statuses are 400 for invalid input, 401 for an invalid or revoked key, 404 when an order is not available to that account, 429 for rate limiting and 500 for a temporary server problem.

Production safety

• Use a unique idempotency_key of 8–80 letters, numbers, underscores or hyphens for every order.
• Retry temporary failures with exponential backoff; do not create a new idempotency key for the same intended order.
• Validate service minimum and maximum quantities before submitting.
• Keep API keys on your server and use separate keys for separate applications.
• Poll order status responsibly instead of sending continuous requests.