API Documentation


Connect your website, app, reseller panel, or automation system to Sizzle Social and place orders directly through our API.

Getting Started

Use this API to fetch services, place supported orders, check order status, request refills, check refill status, and check your balance.

API URL https://app.sizzlesocial.ng/api/v1
HTTP Method POST recommended. Query string requests may also work because the API reads request parameters.
Request Format Form data / URL encoded parameters
Response Format JSON
Your API Key YOUR_API_KEY

Every request must include your API key as key and the API action as action.

POST https://app.sizzlesocial.ng/api/v1key=YOUR_API_KEYaction=services

Services List

ParameterRequiredDescription
keyYesYour API key.
actionYesUse services.

The services list returns active services available to your account. If you have custom pricing, the returned rate reflects your custom price.

Important: rate is stored as price per 1000 units. For digital account services, one account is charged as rate / 1000.

key=YOUR_API_KEYaction=services

Example Response

[
  {
    "service": "1201",
    "name": "Instagram Followers",
    "category": "Instagram",
    "rate": "1500",
    "min": "100",
    "max": "10000",
    "type": "default",
    "desc": "Service description",
    "dripfeed": "1"
  }
]

Place a Normal Order

ParameterRequiredDescription
keyYesYour API key.
actionYesUse add.
serviceYesThe service ID from the services list.
linkYesThe link, username, post URL, profile URL, or target required by the selected service.
quantityYes for normal quantity servicesThe quantity to order. It must respect the service minimum and maximum.
runsOnly for drip-feedNumber of drip-feed runs. Only supported when the service has dripfeed enabled.
intervalOnly for drip-feedInterval between drip-feed runs in minutes. Accepted values are 0, 5, 10, 15, 30, 60, 90.
key=YOUR_API_KEYaction=add
service=1201
link=https://instagram.com/example
quantity=1000

Example Response

{
  "status": "success",
  "order": 32
}

Custom Comments Orders

Use this format only for services whose returned type is custom_comments.

ParameterRequiredDescription
keyYesYour API key.
actionYesUse add.
serviceYesThe custom comments service ID.
linkYesThe post or page link.
commentsYesOne comment per line. The number of lines becomes the order quantity.
key=YOUR_API_KEYaction=add
service=1305
link=https://instagram.com/p/example
comments=First comment
Second comment
Third comment

Digital Account Orders

Digital account services are ordered through the same add action. Instead of sending a social media target link, send the customer delivery email.

For instant digital account services, delivery is sent to the destination email as a white-label email attachment. For manual/sourced digital account services, the order is created as pending for manual delivery.

ParameterRequiredDescription
keyYesYour API key.
actionYesUse add.
serviceYesThe digital account service ID.
quantityYesNumber of accounts required.
destination_emailYesCustomer email address where the digital account file should be delivered.
customer_emailAlternativeAlternative name accepted for the destination email field.
emailAlternativeAlternative name accepted for the destination email field.
linkAlternativeIf no email field is sent, the API will also accept a valid email address in link.

Pricing: Digital account service rates are still stored per 1000. If a service rate is 2780000, one account costs 2780. Ordering 1 account charges 2780000 * (1 / 1000).

key=YOUR_API_KEYaction=add
service=2401
quantity=1
destination_email=customer@example.com

Example Response

{
  "status": "success",
  "order": 1042
}

Check Single Order Status

ParameterRequiredDescription
keyYesYour API key.
actionYesUse status.
orderYesThe order ID returned when the order was created.
key=YOUR_API_KEYaction=status
order=32

Example Response

{
  "order": "32",
  "status": "Pending",
  "charge": "0.0360",
  "start_count": "0",
  "remains": "0",
  "currency": "NGN"
}

Check Multiple Order Statuses

ParameterRequiredDescription
keyYesYour API key.
actionYesUse status.
ordersYesComma-separated order IDs.
key=YOUR_API_KEYaction=status
orders=32,33,34

Example Response

{
  "32": {
    "order": "32",
    "status": "Completed",
    "charge": "0.0360",
    "start_count": "0",
    "remains": "0",
    "currency": "NGN"
  },
  "33": "Incorrect order ID"
}

Refill Request

Use this only for orders and services that support refill. The order must belong to your account.

ParameterRequiredDescription
keyYesYour API key.
actionYesUse refill.
orderYesThe order ID to request refill for.
key=YOUR_API_KEYaction=refill
order=32

Example Response

{
  "status": "success",
  "message": "Refill request created",
  "refill": "15"
}

Refill Status

ParameterRequiredDescription
keyYesYour API key.
actionYesUse refill_status.
refillYesThe refill ID returned by a refill request.
key=YOUR_API_KEYaction=refill_status
refill=15

Possible Statuses

queued, sending, sent, pending, awaiting, inprogress, manual_review, failed, error, rejected, completed, canceled, expired

Balance

ParameterRequiredDescription
keyYesYour API key.
actionYesUse balance.
key=YOUR_API_KEYaction=balance

Example Response

{
  "status": "success",
  "balance": "5000.00",
  "currency": "NGN"
}

Errors and Notes

api_is_disable_for_this_user_or_user_not_found_contact_the_support The API key is missing, invalid, disabled, or attached to an inactive account.
this_action_is_invalid The action value is missing or not supported.
service_id_does_not_exists The service ID does not exist.
not_enough_funds_on_balance Your balance is not enough for the requested order.
quantity_is_required The selected service requires a quantity.
Destination email is required... A digital account service requires a valid destination email.

The API does not currently expose add-funds, coupon, cancellation, ticket, downloads-page, scheduler, or rewards endpoints.

Subscription order status can be returned for existing subscription orders, but subscription order creation is not currently documented here because the API controller does not route the full subscription creation flow.