Pulling Ethiopian (+251) SMS codes into your test pipeline

Which API calls fetch an Ethiopian verification code?

OTP routing for Ethiopia comes down to five plain HTTP calls against https://otproute.com/api/v1. Authenticate each one with a Bearer key beginning or_live_, generated in the Developer console; an account can hold up to 10 keys, so CI, staging and a local laptop can each run on separate credentials.

1. GET /api/v1/countries lists every route, and Ethiopia appears with the id et.
2. GET /api/v1/services returns service ids, while GET /api/v1/prices?country=et&service=<id> reports the current price and availability for the pair you plan to test.
3. POST /api/v1/activations with {"service": "telegram", "country": "et"} reserves a +251 number and hands back an activation id.
4. Type that number into the phone field of the product under test and trigger its SMS.
5. Read the code from a webhook event or by polling GET /api/v1/activations/{id}, and abandon a run cleanly with POST /api/v1/activations/{id}/cancel.

Inventory moves during the day, so call the price endpoint at runtime instead of hard-coding anything. A quick GET /api/v1/balance before the suite starts lets a job stop early when the wallet runs low. Request and response shapes for this SMS verification API are in the developer docs.

How do I wire a signed webhook for +251 activations?

Polling is fine for a single test, but parallel jobs are easier to reason about when events are pushed to you. Register up to 5 webhook endpoints per account and subscribe to activation.sms_received, activation.expired and activation.cancelled.

Every request carries X-OTPRoute-Signature: t=<unix>,v1=<hex>. Recompute HMAC-SHA256 over <t>.<raw body> with the endpoint secret, compare the result to v1 using a constant-time check, and refuse the call when the timestamp is stale. Verify on the raw bytes before any JSON parser touches them.

Assume an event can be delivered more than once: key the handler on the activation id and drop repeats, so a retried event never fills an OTP field twice. If you stay with polling, an interval of a few seconds sits comfortably inside the limit of 300 requests per minute. Our walkthrough on securing OTP webhooks with HMAC includes a reference handler.

Which services can receive Ethiopia SMS OTP codes right now?

The Ethiopia route currently lists more than 1,700 services. Popular entries in the live snapshot include WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, ChatGPT (OpenAI), Microsoft & Outlook, LinkedIn, Uber, Signal, Viber, imo and Netflix.

Treat that list as a snapshot. Availability for any single service can shift within hours, which is why the API reports it live rather than in a static table. Query the countries and prices endpoints at the start of each run, and search the full catalogue in the dashboard if you need something less common.

What should QA teams know about +251 number formats and SMS language?

An Ethiopian number in E.164 is +251 followed by nine digits. Domestically people dial a leading 0 in front of those nine digits, so users will often type 09… into your form. Strip that trunk zero, prepend +251 and store the canonical E.164 string, showing the local style only in the interface. Cover both inputs, plus spaces and dashes, because phone-field validation is where many sign-up bugs hide.

Amharic is the federal working language and is written in the Ethiopic (Ge'ez) script, while Afaan Oromo, Tigrinya and Somali are widely used in their regions. Most international services send codes in English, yet a localised template may come through in Amharic. Extract the digits with a pattern instead of matching surrounding words, and make sure your logs store UTF-8 cleanly.

Teams usually test this route when launching an app for Ethiopian users, checking an Amharic localisation, or serving diaspora customers who register with a home-country number. If your product shows dates, Ethiopia's own calendar is a separate localisation case worth adding. The QA testing page shows how other teams structure such suites.

Can non-developers get an Ethiopia verification number from the dashboard?

Yes. Product managers and support staff can run the same flow without writing code:

1. Create an account with your email and a 6-digit code, or with Google sign-in, then switch on TOTP two-factor.
2. Add funds to the wallet.
3. Pick Ethiopia, choose the service, and read the price shown before confirming.
4. Paste the +251 number into the app you are verifying.
5. Keep the activation open; the code is displayed there once it is received.

Many teams use this path for one-off spot checks while engineers drive the identical route through the API.

What happens when the +251 code never shows up?

Each activation stays open for 20 minutes. You only pay if the code arrives; if the window closes without an SMS, or you cancel, the full amount goes back to the wallet automatically.

When nothing comes through:

• Let the window run before calling it a failure, since timing depends on the service and the route.
• Retry later, or switch to another service route if your test case allows it.
• Confirm the service accepts virtual numbers at all. Some refuse them, and the refund exists for exactly that situation.
• Don't re-order in a tight loop. Space retries out and log each activation id so patterns become visible.

The article on reducing failed OTP deliveries lists further checks.

Is there a long-term Ethiopian line, and how is billing handled?

OTP Route has no self-serve long-term number in Ethiopia. Dedicated Numbers, lines you keep while they renew, are a US and Canada product from $1.95/month. If your team needs a lasting +251 line, email [email protected] to ask; availability depends on local rules and is not guaranteed.

Ethiopian activations draw on a single prepaid USD wallet, with no monthly fee and no plan to pick. Fund it by card or with USDT/USDC stablecoins; a PDF invoice lands in your inbox after every top-up. Before spending real funds on a fresh integration, request sandbox mode for a development account: it returns simulated numbers and codes so the whole flow can be exercised end to end.

Ethiopian test numbers from OTP Route are for verifying products and accounts your organisation genuinely owns; each service's terms still apply, as does our Acceptable Use Policy.

Frequently asked questions

Can I test my app's Ethiopian sign-up flow without a local SIM?

Yes. Order a +251 number for your service from the OTP Gateway, enter it in your app and read the code in the dashboard or through the API. You are charged only if the code arrives.

What is the country id for Ethiopia in the OTP Route API?

It is et. Send et as the country field when creating an Ethiopian activation and when querying prices.

How much does a +251 number for testing cost?

Codes start from $0.20 per code. The exact amount for each service is returned by GET /api/v1/prices and shown in the dashboard before you order.

Should I store Ethiopian phone numbers with the leading zero?

No. Keep the E.164 form, +251 plus nine digits, and drop the domestic 0 whenever a user types it. Apply local formatting only on screen.

Will Ethiopian verification texts arrive in Amharic?

Usually they come in English, though a service may use an Amharic template in Ethiopic script. Parse the digits rather than the wording so either version works.

Can I keep an Ethiopian number for later logins?

Not self-serve, because a one-time number covers a single code. For an account that must sign in again, a Dedicated Number in the US or Canada is the fit, or you can email support to ask about Ethiopia.

Is there a way to try the Ethiopia OTP API without spending wallet funds?

Yes. Ask for sandbox mode on a development account and it will return simulated numbers and codes, so you can test the integration end to end.

Service names are trademarks of their respective owners. OTP Route is not affiliated with them. Use numbers lawfully, follow each service's terms and our Acceptable Use Policy.