Direct API
Bearer-authenticated sending with idempotency, usage reporting, and delivery metadata.
View documentationConnect the tools you already use
Make SMS part of the workflow, not another tab to remember.
Use the SMSLite API, Zapier, Make, CRM webhooks, or spreadsheet-driven processes to trigger messages and receive signed delivery updates.
Connection paths
Choose the level of control your workflow needs.
Zapier and Make
Use a webhook or HTTP module to map recipient, message, and reference fields into SMSLite.
Open connection centreDelivery callbacks
Send signed delivery.updated events back to your workflow when provider callbacks arrive.
See webhook docsTypical send payload
{"recipient":"+27820000000",
"message":"Your order is ready",
"reference":"order-1042"}
"message":"Your order is ready",
"reference":"order-1042"}
Start with a trigger. Finish with a useful status.
The outbound and inbound sides of the workflow stay explicit: your system requests the send, SMSLite records the message, and delivery updates can return through a signed webhook.