Bulk SMS API for
South African applications.

Send an SMS with the HTTPS API

Authenticate on your backend with the account Client ID and Client Secret to obtain a login token. Use that token in the bearer header for sending and balance requests. Keep secrets out of browser/mobile client code, public repositories and support screenshots.

POST https://portal.smsflow.co.za/api/integration/BulkMessages
Authorization: Bearer YOUR_LOGIN_TOKEN
Content-Type: application/json

{
  "SendOptions": {
    "startDeliveryUtc": null,
    "campaignName": "Website synthetic example",
    "checkOptOuts": true
  },
  "messages": [
    {
      "content": "Your demo appointment is confirmed for 10:00.",
      "destination": "27000000000"
    }
  ]
}

The destination is deliberately synthetic. Replace it only with a recipient authorised for a controlled test. Running a real send consumes credits. This website example does not execute a request.

Start with the first SMS quickstart, then check authentication, sending and balance. For the raw requests and Postman collection, use the published HTTP examples.

Choose an integration and handle failures deliberately

.NET / C# quickstart · Node.js quickstart · Python quickstart. SQL worker overview.

Validate destinations and content before sending. Check balance and record the response/reference without logging secrets or customer message bodies. An accepted API request is not proof of handset delivery. Public SDK coverage is authentication, sending and balance; confirm other needs with SMSFlow.

A timeout can leave the send outcome uncertain. Do not blindly replay a batch: it may create duplicate messages and charges. Use the current error and retry reference, distinguish authentication/validation failures from transient faults, and investigate uncertain outcomes before resending.