Skip to main content
Sling API v2 uses bearer token authentication. Every request must include your token in the Authorization header. There are no sessions, cookies, or OAuth flows — just a static token you copy from your dashboard or exchange for through POST /auth.

​
Get your API token

You have two options.

​
Option 1: From the dashboard

1

Log in to your dashboard

Go to app.sling.com.ng and sign in.
2

Open the API token page

Navigate to Account → API.
3

Copy your token

Copy the API token displayed on that page. Treat it like a password — do not share it or commit it to source control.

​
Option 2: Exchange email and password through POST /auth

cURL
curl --request POST \
  --url https://app.sling.com.ng/api/v2/auth \
  --header "Accept: application/json" \
  --header "Content-Type: application/json" \
  --data '{
    "email": "[email protected]",
    "password": "your-password"
  }'
A successful login returns: 
{
  "api_token": "YOUR_API_TOKEN"
}
Store the api_token and use it as a bearer credential for the rest of the API. See POST /auth for the full reference.

​
Add the token to a request

Pass your token as a bearer credential in the Authorization header alongside Accept: application/json. 
curl --request POST \
  --url https://app.sling.com.ng/api/v2/send-sms \
  --header "Accept: application/json" \
  --header "Authorization: Bearer YOUR_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
    "to": "2349123772222",
    "message": "Hello from Sling",
    "sender": "YourSenderID"
  }'
Keep your API token secret. Anyone with your token can send messages and consume your credit balance. If your token is compromised, regenerate it from your dashboard immediately.

​
Authentication errors

SituationResult
POST /auth with wrong email or password400 Bad Request — "message": "Incorrect E-Mail or Password"
Missing or invalid Authorization header401 Unauthorized — request rejected
Token is valid but account has no credit400 Bad Request — "details": "Insufficient credit"
Check that you are copying the full token with no extra spaces or line breaks, and that you are using the Bearer prefix (note the space between Bearer and the token value).