Introduction

Lisoloo is the bulk-SMS API exposed by the Bloonio platform. It accepts a single recipient or a list of thousands, sends now or at a scheduled time, and reports delivery status both synchronously (via GET /status/{id}) and asynchronously (via the callback_url you provide on each request, or the merchant-wide webhook configured on your API key).

How the pieces fit

Three actors:

• Your application backend holds the long-lived api_key. It is the only place that knows the secret.
• The Lisoloo API at $BASE_URL/api/v1/lisoloo/sms-api validates the key on every request, queues the SMS to the underlying carrier connection, and emits delivery receipts.
• Your webhook endpoint receives status updates as the message walks the pending → processing → sent → delivered lifecycle.

The API surface is intentionally small — four endpoints — so most of the documentation here is about request shape, scheduling semantics, and what the delivery receipts mean.

What you get

• One endpoint, three sending modes. POST /send handles instant, scheduled, and recurring sends. The sending_type field switches between them; the body shape changes by scheduled_dates / recurring_schedule. See Sending types.
• Stable status lifecycle. Every message moves through pending → processing → sent → delivered, with failed as a terminal state. See Message lifecycle.
• Webhook delivery receipts. Register a webhook_url on your API key (with optional HTTP Basic auth) and the gateway will POST every status change. See Webhooks overview.
• Multi-recipient pricing. Send to N numbers in one call; you pay per recipient × per SMS-segment. See Character limits.
• Sandbox by default. Separate sandbox and production base URLs are shown on the Bloonio dev portal beside each API key. Every example on this site assumes you’ve exported the right one as BASE_URL. See Environments.

Who this is for

These docs assume you are a backend engineer integrating SMS into your own application. You should be comfortable reading HTTP, JSON, and at least one of cURL, Python, JavaScript, or PHP — every example in this site is provided in all four.

If you are looking for the dashboard, the merchant onboarding flow, or billing — those live in the Bloonio app, not here.

Two API generations

The current Lisoloo SMS API uses a single app-key header for authentication. This is the same model as Lokotroo Auth-v2. A future release will introduce session-token authentication (Auth-v3) for the mobile SDK; the HTTP API documented here will remain available unchanged.

Where to next

Quickstart Send your first SMS from cURL, Python, JavaScript, or PHP in under five minutes.

Authentication How the app-key header works and where to keep it safe.

API reference Every endpoint, parameter, schema, and response — driven by the OpenAPI spec.

Webhooks Receive asynchronous delivery receipts on your own server.