API v3

API docs

API reference for SMM Africa. Check balances, fetch services, place orders, and track status from one endpoint.

Download OpenAPI 3 spec (JSON)Download Postman collection

Base URLhttps://smm.africa/api/v3

FormatPOST · JSON or form fields · JSON response

Your API keyIssued per account. Pull it from Account once you sign in.

Start with a balance check

A balance request is the fastest way to confirm your key, request format, and that the integration round-trips before you start placing orders.

Code example language

POST /api/v3 · balance

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "balance"
}'

HTTP 200 · balance

{
  "balance": "100.84",
  "currency": "USD"
}

Authentication

Send your account API key either in Authorization: Bearer YOUR_API_KEY or as the key request field. Choose one method; the key field works with common reseller panels. Keep keys in server-side environment variables and rotate them from Account.

All actions use POST https://smm.africa/api/v3. Supported bodies: application/json, application/x-www-form-urlencoded, and multipart/form-data with text fields only. Responses are JSON. The action field selects the operation.

curl · form authentication

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  --data-urlencode "key=YOUR_API_KEY" \
  --data-urlencode "action=balance"

All balances, charges, and order amounts in v3 are returned in USD for compatibility.

Reference

Full endpoint reference

Review the request parameters, sample responses, and the exact behavior for each supported action.

balance

Check the wallet balance tied to the authenticated reseller API key.

POST

Code example language

POST /api/v3 · balance

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "balance"
}'

Request parameters

Parameter	Type	Required	Description & constraints
`key`	string	Conditional	Your API key, used to authenticate the request. Required only when Authorization: Bearer is absent.
`action`	string	Yes	balance Use the exact action value shown.

Example response

HTTP 200 · balance

{
  "balance": "100.84",
  "currency": "USD"
}

All balances, charges, and order amounts in v3 are returned in USD for compatibility.

Example error response

HTTP 400 · balance

{
  "error": "Invalid API key"
}

services

Fetch the live SMM Africa service catalog with service IDs, pricing, limits, and refill or cancel flags.

POST

Code example language

POST /api/v3 · services

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "services"
}'

Request parameters

Parameter	Type	Required	Description & constraints
`key`	string	Conditional	Your API key, used to authenticate the request. Required only when Authorization: Bearer is absent.
`action`	string	Yes	services Use the exact action value shown.

Example response

HTTP 200 · services

[
  {
    "service": 1,
    "name": "Service Name",
    "type": "Default",
    "rate": "0.90",
    "min": "50",
    "max": "10000",
    "category": "First Category",
    "description": "Service Description",
    "refill": true,
    "cancel": true,
    "drop_rate": "Almost No",
    "start_time": "2 mins",
    "speed": "12 mins",
    "reliability": "Poor"
  }
]

Fetch the live catalog before ordering because service IDs, rates, limits, and availability can change.

Example error response

HTTP 400 · services

{
  "error": "Invalid API key"
}

add

Place a new social media growth order with service ID, target link, and quantity.

POST

Code example language

POST /api/v3 · add

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "add",
  "service": 1234,
  "link": "https://instagram.com/your-profile",
  "quantity": 500,
  "idempotency_key": "order-unique-001"
}'

Request parameters

Parameter	Type	Required	Description & constraints
`key`	string	Conditional	Your API key, used to authenticate the request. Required only when Authorization: Bearer is absent.
`action`	string	Yes	add Use the exact action value shown.
`service`	integer	Yes	The ID of the service you want to order. Use an ID from the current services response; its type determines the fields below.
`link`	string	Conditional	The target profile, post, or content URL. Required for the selected service type; supply the target URL.
`quantity`	integer	Conditional	The quantity you want to order. Must satisfy the selected service's min and max. Omit when its type does not accept quantity.
`idempotency_key`	string	Recommended	Use one unique value per logical order. If the request times out without a response, retry with the same value so the order cannot be charged twice. Persist a unique value per logical order; reuse only with an identical retry payload.

Fields by service type

Select the type returned by services; do not send a separate type field. List values are newline-separated text, including in JSON. The API derives billable quantity for comments, custom lists, packages, and subscriptions, then checks service limits.

Service type	Required fields	Optional fields / constraints
Default	`link, quantity`	Standard target URL and requested quantity.
Package	`link`	No quantity.
SEO	`link, quantity, keywords`	Put one keyword on each line.
Custom Comments	`link, comments`	One comment per line; the comment count is the order quantity.
Custom Comments Package	`link, comments`	One comment per line; no quantity.
Comment Replies	`link, username, comments`	username is the comment owner; put one reply per line.
Comment Likes	`link, username`	username is the comment owner; no quantity.
Mentions	`link, quantity, usernames`	Put one username per line.
Mentions with Hashtags	`link, quantity, usernames, hashtags`	Put usernames and hashtags on separate lines.
Mentions Custom List	`link, usernames`	Put one username per line; no quantity.
Mentions Hashtag	`link, quantity, hashtags`	Put one hashtag per line.
Mentions User Followers	`link, quantity, username`	username is the source profile URL to scrape.
Mentions Media Likers	`link, quantity, media`	media is the source media URL to scrape.
Poll	`link, quantity, answer`	answer is the exact poll-option text expected by the provider.
Invites from Groups	`link, quantity, groups`	Put one group on each line.
Subscriptions	`username, min, max, delay`	No link or quantity. posts, old_posts, and expiry are optional. delay must be 0 or a 5-minute interval through 600; use DD/MM/YYYY for expiry.
Web Traffic	`quantity, country, device, type_of_traffic`	device is mobile or desktop. type_of_traffic is 1 (requires google_keyword), 2 (requires referring_url), or 3.

Optional attribution fields

Parameter	Type	Required	Description & constraints
`goal_key`	string	No	Optional goal key for guided-growth attribution. Optional attribution metadata.
`recommendation_tier`	string	No	Optional recommendation tier. Optional attribution metadata.
`user_intent_label`	string	No	Optional label describing the user’s intent. Optional attribution metadata.
`source_flow`	string	No	Optional identifier for the flow that created the order. Optional attribution metadata.

Example response

HTTP 200 · add

{
  "order": 1000000,
  "charged": 5.85,
  "queued": true
}

Store the returned order ID, and check status before retrying an add request.

Example error response

HTTP 400 · add

{
  "error": "Invalid API key"
}

status

Poll an order by ID to read delivery state, start count, remains, and charge details.

POST

Code example language

POST /api/v3 · status

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "status",
  "order": 1000000
}'

Request parameters

Parameter	Type	Required	Description & constraints
`key`	string	Conditional	Your API key, used to authenticate the request. Required only when Authorization: Bearer is absent.
`action`	string	Yes	status Use the exact action value shown.
`order`	integer / string	Yes	The SMM Africa order ID returned by add. Use the order ID returned by add for follow-up requests.

Example response

HTTP 200 · status

{
  "order": 1000000,
  "status": "processing",
  "start_count": 3572,
  "remains": 157,
  "charge": 0.27819
}

Poll one order per status request. Stagger requests and honor Retry-After when rate limited.

Example error response

HTTP 400 · status

{
  "error": "Order not found"
}

refill

Request a refill for an eligible order inside the published refill window.

POST

Code example language

POST /api/v3 · refill

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "refill",
  "order": 1000000
}'

Request parameters

Parameter	Type	Required	Description & constraints
`key`	string	Conditional	Your API key, used to authenticate the request. Required only when Authorization: Bearer is absent.
`action`	string	Yes	refill Use the exact action value shown.
`order`	integer / string	Yes	The SMM Africa order ID returned by add. Use the order ID returned by add for follow-up requests.

Example response

HTTP 200 · refill

{
  "order": 1000000,
  "success": "Refill request accepted."
}

Refill is available only for eligible orders within the service’s published refill window.

Example error response

HTTP 400 · refill

{
  "error": "Invalid API key"
}

cancel

Request cancellation for an order where the selected service supports cancellation.

POST

Code example language

POST /api/v3 · cancel

curl --fail-with-body --silent --show-error --max-time 60 \
  -X POST https://smm.africa/api/v3 \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $SMM_AFRICA_KEY" \
  -d '{
  "action": "cancel",
  "order": 1000000
}'

Request parameters

Parameter	Type	Required	Description & constraints
`key`	string	Conditional	Your API key, used to authenticate the request. Required only when Authorization: Bearer is absent.
`action`	string	Yes	cancel Use the exact action value shown.
`order`	integer / string	Yes	The SMM Africa order ID returned by add. Use the order ID returned by add for follow-up requests.

Example response

HTTP 200 · cancel

{
  "order": 1000000,
  "success": "Cancellation request accepted."
}

Cancellation is available only when the selected service supports it.

Example error response

HTTP 400 · cancel

{
  "error": "Invalid API key"
}

Errors & retries

Check the HTTP status and the JSON error field. Authentication errors use HTTP 400; API callers are not redirected to login. Log technical errors privately and show customers a neutral message.

HTTP 400 · application/json

{
  "error": "Invalid API key"
}

HTTP	Error / condition	What to do
400	`Invalid API key`	Check the key and required fields. Correct the request before retrying.
402	`Insufficient balance`	Fund the account wallet before submitting the order again.
409	`A matching API order request is already being processed`	Wait before retrying the identical request with its original idempotency key.
409	`This idempotency key was already used for a different API order request`	Restore the original payload for a retry. Use a new key only for a new logical order.
415	`Unsupported content type`	Send JSON, URL-encoded form fields, or multipart text fields.
423	`Account suspended (message varies)`	Resolve the account restriction with support; do not retry repeatedly.
429	`Too many requests. Please slow down and try again shortly.`	Wait for the Retry-After interval, then retry with backoff.
500 / 503	`Server failure or temporary unavailability (message varies)`	Back off. For order submissions, keep the same payload and idempotency key.

Retry an order without charging twice

Create and persist a unique idempotency_key for each logical order before sending add. Replace the example key with your own unique value.
Allow up to 60 seconds for the server request. After 20 seconds, show a pending message to the customer while the backend request continues.
If no response arrives, retry the exact same payload with the same key after a delay. Do not generate a new key. A completed retry replays the response with X-Idempotent-Replay: true.
Once you receive an order ID, save it and use status to track that order. A queued response means accepted for fulfillment, not completed delivery.

Idempotency-Key and X-Idempotency-Key headers are also supported. Without a client key, an order can still be submitted, but retrying after a timeout cannot safely identify the original attempt.

Rate limits

Limits are action-specific and deployment-configurable. On HTTP 429, honor Retry-After (seconds). Without that header, use exponential backoff with jitter, for example 2, 4, 8, then 16 seconds plus a small random delay. Bound retries and surface persistent failures to your operator.

Cache the catalog fetched with POST /api/v3 and action=services. Refresh it periodically and verify current service IDs, rates, and min/max constraints before ordering.

Order lifecycle

Send action=status with one order ID per request. As a starting client policy, poll every 30 seconds, then increase the interval for long-running orders; honor rate limits. Stagger requests across orders. Webhooks are not currently supported.

queued → pending → processing: Active states: continue polling. Orders may skip intermediate states.
completed · partial · refunded · canceled: Terminal states: stop routine delivery polling. Partial means delivery was incomplete; inspect charge and remains. Refill and cancellation requests are subject to service and order eligibility.
unknown: An unrecognized state; do not treat it as success or place a replacement order automatically. Retry status with backoff and contact support if it persists.

Integration notes for production use

Treat the API like infrastructure. These notes cover the things that matter once you are running automated orders, a client panel, or a high-volume storefront.

Shared wallet balance

Direct orders, storefront orders, and API orders all draw from the same wallet balance. Fund it from any channel, use it from any channel.

Secure your key

Never expose the key, API hostname, configured provider name, or raw transport errors in client-side code or storefront messages. Proxy calls through your backend, log technical details privately, and after 20 seconds show customers neutral wording such as: Order submission is taking longer than expected. Check your orders before trying again.

Quick answers

How do I get an API key?

Is the API free?

There is no extra API fee. You only pay for services you order. The same wallet funds direct orders, storefront orders, and API orders.

What are the rate limits?

Limits are action-specific and can change. Space bulk calls, batch status polls, and when the API returns 429 wait for the Retry-After interval before retrying.

How should I handle retries?

Send one unique Idempotency-Key header or idempotency_key field for each logical add order. If the request times out, retry the identical payload with the same key so a completed attempt is replayed without another charge.

Is there a webhook?

Status polling is the supported path today. Hit the status action for orders you are watching and cache the result in your own system.

Which countries are supported?

The API is available worldwide, with strong support for African markets and M-Pesa-friendly wallet funding.

API vocabulary

Terms resellers should understand

Reseller API: A server-to-server interface that lets another panel or workflow place and track SMM Africa orders from its own application.
Service catalog: The live list of service IDs, prices, limits, refill support, and cancellation support used before placing an order.
Action: The JSON field that chooses the API operation, such as balance, services, add, status, refill, or cancel.
Wallet-backed ordering: An ordering model where direct, storefront, and API orders all draw from the same funded SMM Africa wallet balance.