Skip to content

Quickstart

You will obtain an API key from the developer portal, then send a single SMS to your own phone. By the end you will have a message_id and a pending status from the sandbox.

Open the developer portal in the Bloonio dashboard, switch to the API keys tab, and click Generate API key. The cleartext api_key is shown exactly once. Copy it into a secret store immediately — it is not recoverable from the database after the banner closes.

See API keys for the full management flow, including rotation and webhook configuration.

The exact same call works from any language. Pick the tab matching your stack.

Terminal window
curl $BASE_URL/api/v1/lisoloo/sms-api/send \
-X POST \
-H "app-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": ["+243998857000"],
"message": "Hello from Lisoloo!",
"sender_id": "MYAPP"
}'

You get back, on success:

{
"status_code": 201,
"data": {
"message_id": "507f1f77bcf86cd799439011",
"total_recipients": 1,
"total_messages": 1,
"total_cost": 0.02,
"currency": "USD",
"status": "pending",
"sending_type": "immediate"
}
}

Within a few seconds the message will move from pending to processing to sent to delivered. You can poll GET /status/{message_id} to see the transitions, or wait for the webhook to fire (if configured).

Terminal window
curl $BASE_URL/api/v1/lisoloo/sms-api/status/507f1f77bcf86cd799439011 \
-H "app-key: YOUR_API_KEY"
  1. You authenticated to the gateway with the app-key header.
  2. The gateway validated the key, computed the cost (1 SMS × 1 recipient × unit price), and queued the message.
  3. The carrier connector picked it up, sent it through the network, and reported a delivery receipt back to the gateway.
  4. The gateway emitted the receipt to your callback_url if you set one, or to the webhook configured on your API key.