SDKs
Use an official SDK for typed helpers, automatic retries, phone-number normalization, and consistent error handling around the public API. The REST API remains the canonical integration surface, and every SDK is a real, versioned, open-source package.
Dive into the official SDK documentation at sdk.sendafrica.online .
| Language | Install | Runtime | Official SDK docs | Full reference |
|---|---|---|---|---|
| Go | go get github.com/SendAfrica/GO-SDK | Go 1.22+ (stdlib only) | Go SDK | Local guide |
| Python | pip install sendafrica | Python 3.9+ (requests; async: httpx) | Python SDK | Local guide |
| TypeScript / Node.js | npm install sendafrica | Node.js 18+ (native fetch) | TypeScript SDK | Local guide |
Quickstart
Go
client := sendafrica.NewClient(os.Getenv("SENDAFRICA_API_KEY"))
result, err := client.SMS.Send(ctx, sendafrica.SendSMSRequest{
To: "0712345678", Message: "Your verification code is 4921.",
})Python
client = SendAfrica(api_key=os.environ["SENDAFRICA_API_KEY"])
result = client.sms.send(to="0712345678", message="Your verification code is 4921.")TypeScript
const client = new SendAfricaClient({ apiKey: process.env.SENDAFRICA_API_KEY! })
const result = await client.sms.send({ to: '0712345678', message: 'Your verification code is 4921.' })What every SDK covers
- Single SMS, client-side send-many (rate limited), server-side bulk SMS, and message logs
- Credit balance and transaction history
- The published international rate card
- Sender ID registration, verification, and management
- Pay-as-you-go credit top-ups (vouchers)
- Webhook signature verification for delivery events
- Local phone-number normalization and SMS part/credit estimation
All three SDKs authenticate with your server-side API key, retry transient failures, and map API errors to typed language-native exceptions. If your language is not covered, use the REST examples in the API reference and keep the same server-side credential and webhook rules in every implementation.
Last updated on