Verify Uganda phone numbers with a code by SMS and, when the SMS does not land, by email. Point your SDK at uganda.woyra.io and the sender rules, currency and data region are set for you.
UCC requires sender ID registration.
Opt-out keywords honoured automatically: STOP, UNSUBSCRIBE, CANCEL, END, QUIT.
uganda.woyra.ioGlobal
curl -X POST https://uganda.woyra.io/v1/verifications \
-H "Authorization: Bearer $WOYRA_KEY" \
-H 'Content-Type: application/json' \
-d '{"to": "+256712345678", "email": "abebe@example.com", "channels": ["sms", "email"]}'
# Later, when the user types the code:
curl -X POST https://uganda.woyra.io/v1/verifications/ver_01J.../check \
-H "Authorization: Bearer $WOYRA_KEY" \
-d '{"code": "483920"}'The same key works on every endpoint. Calling uganda.woyra.io applies Uganda's rules and, where residency requires it, keeps the data in the global region.
Alphanumeric sender IDs, registration required · billed in USD · global data region
Uganda allows an alphanumeric sender but requires the name to be registered with the operators before traffic flows under it. Woyra files that registration and tells you when it is live; until then your traffic goes out on a sender that is already cleared, so nothing waits on paperwork.
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.
Every message to Uganda 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.
An account on the Uganda endpoint is billed in US dollars today. Billing in USD 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.
Uganda allows alphanumeric sender IDs, so a message can arrive from your brand name rather than a number. The sender ID must be registered first; Woyra files the registration and tells you when it is live.
USD. Prepaid, with a hard spend cap you set on each project.
Global
E.164: a plus, the country code +256, then the subscriber number, as in +256712345678. 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.
uganda.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.