South Africa · +27 · billed in ZAR

OTP verification API in South Africa

Verify South Africa phone numbers with a code by SMS and, when the SMS does not land, by email. Point your SDK at southafrica.woyra.io and the sender rules, currency and data region are set for you.

Verify in South Africa: the rules

Alphanumeric sender IDs allowed

POPIA governs personal information. Opt-out must be honoured within a reasonable period and free of charge.

Opt-out keywords honoured automatically: STOP, UNSUBSCRIBE, CANCEL, END, QUIT.

Endpoint, currency, data

Endpoint
southafrica.woyra.io
Currency
ZAR
Dialling code
+27
Data region
global
Price
$0.01 per successful verification

Global

Your first Verify call from South Africa

curl -X POST https://southafrica.woyra.io/v1/verifications \
  -H "Authorization: Bearer $WOYRA_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"to": "+27712345678", "email": "abebe@example.com", "channels": ["sms", "email"]}'

# Later, when the user types the code:
curl -X POST https://southafrica.woyra.io/v1/verifications/ver_01J.../check \
  -H "Authorization: Bearer $WOYRA_KEY" \
  -d '{"code": "483920"}'

The same key works on every endpoint. Calling southafrica.woyra.io applies South Africa's rules and, where residency requires it, keeps the data in the global region.

What sending verify to South Africa involves

Alphanumeric sender IDs, no registration · billed in ZAR · global data region

Your brand name, from the first send

South Africa allows an alphanumeric sender, and asks for no registration to use one. Set `from` to your brand and the message arrives under it. Nothing to file, nothing to wait for, which is the exception rather than the rule in this part of the world.

When the SMS does not land in South Africa

Ask for SMS and email in one verification and the code falls through to email when the SMS is not delivered in time. The person sees one code and one input box. On routes where filtering is common this is the difference between a sign-up completed and a sign-up abandoned, and you wrote none of it.

Which carrier carried it, and why

Every message to South Africa records the carrier it went out on, the score that carrier held at the time, the reason it was chosen and what it cost. It is on the message in the API response and in your logs. Carriers are scored on whether codes are actually entered, not on whether a receipt said OK.

Prepaid, with a cap you set

An account on the South Africa endpoint is billed in US dollars today. Billing in ZAR is where this is going, and it is a real advantage when it arrives, but a converted price needs a published rate behind it and there is not one yet, so we quote one currency rather than invent a second. Funds are reserved at the published price when a message is accepted and settled when it is delivered; a message we never deliver is never charged for, and a hard spend cap you set is enforced rather than invoiced.

Questions about South Africa

Which sender will my codes arrive from in South Africa?

South Africa allows alphanumeric sender IDs, so a message can arrive from your brand name rather than a number, with no registration needed.

What currency am I billed in for South Africa?

ZAR. Prepaid, with a hard spend cap you set on each project.

Where is the phone number of a user in South Africa stored?

Global

What does a South Africa phone number look like in the API?

E.164: a plus, the country code +27, then the subscriber number, as in +27712345678. Woyra strips spaces, hyphens, brackets and a leading 00, but it will not guess a missing country code, because the same digits belong to a different subscriber in every country.

Which endpoint should I call for South Africa?

southafrica.woyra.io, though the same API key works on every endpoint Woyra runs. Which one you call decides the compliance rules applied, the currency you are billed in, and — where residency requires it — which data plane answers.

Also in South Africa