eSMSAfrica

Developer guides

Get from API key to production: quickstarts in four languages, testing, webhooks, errors and SMPP, with links to the full API reference.

These guides walk through the tasks developers do when they add eSMS Africa to an app or a platform. They show the smallest working example and explain the decisions around it, then link to the API reference at docs.esmsafrica.io for every parameter.

SDK quickstarts

Send your first message from Node.js, Python, PHP or Go.

Testing and sandbox

Build and test without sending real SMS or spending credit.

Messaging APIs

OTP verification, bulk and batch sends, and number formatting.

Webhooks and delivery reports

Receive delivery receipts and replies on your server, and verify signatures.

Errors and troubleshooting

What every error code means and how your code should react.

SMPP

Connect an existing SMS platform over SMPP 3.4.

Going live

Everything to check before you switch to a live key.

Frequently asked questions

Where is the full API reference?

At docs.esmsafrica.io/docs/api-reference. These guides explain tasks and link to the reference for every endpoint and parameter.

Can I test without being charged?

Yes. Create a test key (esms_test_...) on the API keys page. Test sends are simulated: nothing is delivered and nothing is charged, and magic numbers let you force each delivery outcome.

Which languages have an official SDK?

Node.js, Python, PHP and Go. You can also call the HTTPS API directly from any language.

Should I use the HTTP API or SMPP?

Use the HTTPS API for apps and websites. SMPP suits existing SMS platforms and aggregators that already speak SMPP 3.4; it needs an allowlisted IP address.

Still stuck?

Our support team answers in the chat, by email and on WhatsApp +254 114 494147.