Testing Angolan (+244) phone verification without a local SIM

Who actually needs a +244 number for testing?

Most requests for an Angolan verification number come from teams that are not physically in Luanda. A product group adding Portuguese-speaking markets often tests Angola next to Brazil, Portugal and Mozambique, and each of those has its own number format and sender behaviour. QA engineers want proof that the sign-up screen accepts a nine-digit +244 mobile, that the country picker defaults correctly, and that the SMS step completes. Operations staff sometimes need a +244 number to confirm a business profile without exposing an employee's personal phone.

If that sounds like your backlog, the QA testing playbook shows how teams fold OTP checks into a regression suite.

Which services work on Angolan routes right now?

The live snapshot for Angola lists familiar names first: WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, ChatGPT (OpenAI), Microsoft & Outlook, LinkedIn, Uber, Signal and Viber. In total the country carries more than 1,600 services.

Need an Angola verification number for a service that is not listed? Search the catalogue first, then treat any list as a starting point, not a promise. Inventory moves through the day, which is exactly why GET /api/v1/prices returns availability together with the price. Read it right before each order rather than caching it overnight.

How do I order an Angolan number from code?

Point your client at https://otproute.com/api/v1 and send a Bearer key that begins with or_live_; keys live in the Developer console. The sequence is short:

1. Look up ids with GET /api/v1/countries and GET /api/v1/services. Angola is ao.
2. Confirm price and stock with GET /api/v1/prices?country=ao&service=<id>.
3. Create the order: POST /api/v1/activations with {"service": "telegram", "country": "ao"}.
4. Type the returned +244 number into the app you are testing.
5. Wait for activation.sms_received on your webhook, or poll GET /api/v1/activations/{id}.

Webhooks are signed with X-OTPRoute-Signature. Recompute HMAC-SHA256 over <t>.<raw body> with the endpoint secret, reject stale timestamps, and key your handler on the activation id so a retried delivery changes nothing. The same SMS verification API handles OTP routing for every other country, so an Angola client is reusable later; the API integration guide walks through one.

Storing +244 numbers and parsing Portuguese messages

Angola runs a closed nine-digit plan with no domestic trunk prefix, and mobile numbers start with 9. That makes normalisation simple: strip spaces and dashes, keep the leading +244, and never insert a 0 in front of the subscriber part. A clean E.164 value has 12 digits after the plus sign.

Portuguese is the official language, so many senders write the surrounding text in Portuguese while others default to English. Accented characters can push a message into Unicode encoding, which changes how it is split into segments. None of that matters if your parser pulls the digit group out of the body instead of matching a fixed phrase, which is the safer habit for any Lusophone market.

The Luanda test is stuck: what now?

A silent number usually has a dull explanation. Work through these before escalating:

• Let the 20-minute window run; late arrivals still count, and an unused order refunds itself.
• Check that the service accepts virtual numbers for Angolan accounts. Some platforms decline them, which is why the refund rule exists.
• Retry a little later, or test the same flow on a different service route.
• Avoid re-ordering in a tight loop; spacing attempts out protects both your wallet and your sender reputation.

Our note on reducing failed OTP deliveries lists further checks.

Long-term lines, wallet and sandbox

There is no self-serve long-term Angolan number. Dedicated lines are a United States and Canada product from $1.95/month, with inbound SMS, outbound SMS and browser calling. If your team needs a persistent +244 line, email [email protected]; whether it can be arranged depends on local rules.

Billing runs from one prepaid USD wallet with no monthly fee and no plan to choose. Top up by card or with USDT/USDC, and every top-up arrives with a PDF invoice. For integration work, ask for a sandbox account, which returns simulated numbers and codes so CI runs spend nothing. Current per-service prices are on the pricing page.

Frequently asked questions

Can I verify my app's Angola sign-up flow without being in Angola?

Yes. Order a +244 number from the OTP Gateway, enter it in your app, and read the code in the dashboard or through the API, wherever your team sits.

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

Angola is ao. Use it in the country field of POST /api/v1/activations and in the country query parameter of GET /api/v1/prices.

Do Angolan numbers need a leading 0?

No. Angola has no domestic trunk prefix, so a mobile is written as +244 followed by nine digits starting with 9, and that is how you should store it.

How much does a +244 number for testing cost?

Prices start at $0.20 per code and vary by service. The dashboard and GET /api/v1/prices show the exact figure before you commit.

What happens if the SMS never arrives?

If nothing comes in during the 20-minute window, or you cancel first, the full amount returns to your wallet automatically. You pay only for codes that actually arrive.

Can I keep an Angolan number for repeat logins?

Not self-serve. Long-term dedicated numbers are sold only for the US and Canada; for an Angolan line, email [email protected] and the team will say whether local rules allow it.

Is there a way to test the integration without spending money?

Yes. A development account can be switched to sandbox on request, and it returns simulated numbers and codes so you can exercise the full flow end to end.

Are there rules on how I use Angolan numbers?

Use them to test or operate your own legitimate products and accounts, follow each service's terms, and stay within the OTP Route Acceptable Use Policy.

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.