Nexra
Start in the sandbox
All connectors

Africa's Talking

Messaging

Send the right update through Africa's Talking at the right moment, with a person approving what reaches customers.

2 ways to read, 3 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Africa's Talking with Nexra

Connected, approved, proven.

The things teams do most with Africa's Talking, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Send an SMSmessages.sendApproval by rule
  • Make a voice callvoice_calls.sendApproval by rule
  • Get account balanceapplication_balances.getRead

Example flow

  1. Africa's Talking · Get account balanceapplication_balances.getDone
  2. Africa's Talking · Send an SMSmessages.sendMaker-checker
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Africa's Talking.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Africa's Talking
  • Africa's Talking's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect a Africa's Talking test account before you go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Africa's Talking: send SMS, voice calls and WhatsApp messages, read incoming messages and your balance; delivery reports and incoming messages as triggers.

Africa's Talking API docs
Source actions
2
Destination actions
3
Data types
5

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

application balances1
  • Get account balanceSource

    The balance of your Africa's Talking account.

inbound messages1
  • List incoming messagesSource

    Text messages people sent to your short code or number, oldest first after the last one read.

messages1
  • Send an SMSDestinationNot retried automaticallyApproval before production

    Sends a text message to one or more numbers from your sender ID or short code.

voice calls1
  • Make a voice callDestinationNot retried automaticallyApproval before production

    Calls one or more numbers from your Africa's Talking voice number; your voice callback decides what the call says.

whatsapp messages1
  • Send a WhatsApp messageDestinationNot retried automaticallyApproval before production

    Sends a WhatsApp text or approved template from your WhatsApp number (Africa's Talking WhatsApp is in preview).

Access and limits

Authentication
Africa's Talking app username and API key
Plans and access
An Africa's Talking account and app with credit; messages and calls are billed. Sender IDs, short codes, voice numbers and WhatsApp numbers are approved per country by Africa's Talking.
Test environment
The sandbox app (username sandbox) sends SMS to Africa's Talking's simulator and costs nothing. Voice and WhatsApp run on live accounts only.
Rate limits
Africa's Talking publishes no fixed limits; Nexra backs off on 429 and never repeats a send.
Pagination
Incoming messages page with lastReceivedId, the last message ID read.
Provider events
Africa's Talking posts delivery reports and incoming messages, form-encoded and unsigned, to the callback addresses set in your app's SMS settings. Flows can start the moment something happens: when an SMS is delivered or fails; when someone texts your short code or number.

Before you build a flow

  • Sending is billable and approval-gated like other message sends; Africa's Talking has no idempotency key for messages, so an uncertain send is never repeated.
  • Voice calls and WhatsApp messages run on live accounts only; Africa's Talking documents no sandbox for them, and WhatsApp is in preview.
  • Callbacks are not signed: the trigger address carries a private key.
  • Phone numbers of people you message or who write to you are masked in results.
  • Airtime, mobile data, USSD and premium SMS subscriptions are not offered.

Developer reference

  1. Create the Africa's Talking credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Africa's Talking, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Africa's Talking docsAPI referenceAfrica's Talking docsAuthenticationAfrica's Talking docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/africas-talking and the Connections API.