Ethiopia · +251 · billed in ETB

Transactional email API for Ethiopia

Receipts, alerts and one-time codes by email to customers in Ethiopia, from a domain you verify once. Billed in ETB on the same account and key as your SMS.

Email in Ethiopia: the rules

Alphanumeric sender IDs allowedSender ID must be registered

Personal data must remain inside Ethiopia under Proclamation 1321/2024. Alphanumeric sender IDs require registration with the operator via Ethio Telecom.

Opt-out keywords honoured automatically: STOP, UNSUBSCRIBE, CANCEL, END, QUIT, አቁም, ተወው.

Endpoint, currency, data

Endpoint
ethiopia.woyra.io
Currency
ETB
Dialling code
+251
Data region
ethiopia
Price
$0.30 per 1,000 emails, first 3,000 a month free

Ethiopia (in-country, Proclamation 1321/2024)

Your first Email call from Ethiopia

curl -X POST https://ethiopia.woyra.io/v1/emails \
  -H "Authorization: Bearer $WOYRA_KEY" \
  -H 'Idempotency-Key: receipt-4821' \
  -H 'Content-Type: application/json' \
  -d '{
    "from": "receipts@yourdomain.com",
    "to": "abebe@example.com",
    "subject": "Your receipt for order 4821",
    "text": "Thank you. Your order is confirmed."
  }'

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

What sending email to Ethiopia involves

Alphanumeric sender IDs, registration required · billed in ETB · ethiopia data region

Email does not change at the border

Mail to Ethiopia is carried the way mail is carried everywhere: a domain you verify once, DKIM keys Woyra generates, bounces and complaints suppressed automatically. What the Ethiopia endpoint changes is the account around it — ETB billing, and the ethiopia data region.

Your Ethiopia data stays in Ethiopia

Proclamation 1321/2024 requires personal data about Ethiopians to stay in the country. Rather than promise that and route around it, Woyra runs a separate Ethiopian data plane: an Ethiopian account's personal data is held there, and a cross-region read is refused outright with a 451 rather than logged and permitted.

Prepaid, with a cap you set

An account on the Ethiopia endpoint is billed in US dollars today. Billing in ETB 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.

One key, both directions

The same key sends SMS and one-time codes to +251 numbers, and the same domain receives: add the MX record and every address on it is an inbox, with replies linked to the email they answer.

Questions about Ethiopia

Is email delivery different in Ethiopia?

No. Email is carried the same way everywhere; what changes is the account: ETB billing and the ethiopia data region.

Where is the email address of a customer in Ethiopia stored?

Ethiopia (in-country, Proclamation 1321/2024)

Can I send SMS and email to Ethiopia from one account?

Yes. One key covers email, SMS, verification and lookup, and a verification can use both channels in one request.

What does a Ethiopia phone number look like in the API?

E.164: a plus, the country code +251, then the subscriber number, as in +251712345678. 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 Ethiopia?

ethiopia.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 Ethiopia