Skip to main content
Sling uses bearer token authentication. Every API 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 and attach to each call.

​
Get your API token

1

Log in to your dashboard

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

Open the API token page

Navigate to Account → API in your dashboard.
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.
4

Add the token to your requests

Include the token in the Authorization header of every API request using the format below.

​
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/v1/send-sms \
  --header "Accept: application/json" \
  --header "Authorization: Bearer YOUR_API_TOKEN" \
  --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.

​
URL-based authentication

For environments where setting HTTP headers is not possible — such as webhooks, redirects, or simple URL requests — you can pass your token as a query parameter instead: 
https://app.sling.com.ng/api/v1/send-sms?api_token=YOUR_API_TOKEN&to=2349123772222&message=Hello&sender=YourSenderID
Prefer header-based authentication wherever possible. URL query parameters can appear in server logs and browser history, which increases exposure risk.

​
Authentication errors

If your token is missing or invalid, the API returns an error response. Common scenarios:
SituationResult
No Authorization header and no api_token query param401 Unauthorized — request rejected
Token is present but invalid or revoked401 Unauthorized — request rejected
Token is valid but account has no credit400 Bad Request — "details": "insufficient credit"
Check that you are copying the full token from your dashboard with no extra spaces or line breaks, and that you are using the Bearer prefix (note the space between Bearer and the token value).