Testing Mozambican sign-ups when nobody on the team holds a +258 SIM

Our Mozambique launch is stuck on phone verification. Where do we start?

The usual story: the app is translated, the payment screens are ready, and the last open ticket says someone must confirm that a Mozambican customer can actually finish sign-up. Nobody has a +258 SIM, roaming is slow to arrange, and a colleague's personal phone is not a test fixture.

The OTP Gateway removes that dependency. You request a +258 number for one specific service, use it once on the screen under test, and the incoming code comes back to you. It suits QA and test automation, launch checklists, and support teams reproducing a customer's report without borrowing anyone's handset.

What does a +258 number look like, and how should we store it?

Mozambique's country code is +258, and national numbers are nine digits long with no trunk zero to strip, so the local and international forms differ only by the country code. Mobile numbers begin with 8. In practice that means:

• Persist the E.164 form, +258 followed by the nine digits, and format for display separately.
• Reject entries that add a leading zero out of habit from other markets, or quietly remove it before validation.
• Keep the country code even for users who only ever dial locally; your SMS sender and any webhook consumer need it.

Portuguese is the official language, so messages may arrive in Portuguese or in English depending on the service and the locale of the account. If your own templates are Portuguese, check how accented characters such as ç and ã render, since non-ASCII text changes SMS encoding and can split a message into more parts.

Which services can send a code to a Mozambique verification number?

Across all services, the snapshot for Mozambique counts more than 1,600. Frequently requested ones include WhatsApp, Telegram, Facebook, Instagram, Google (Gmail & YouTube), Microsoft & Outlook, LinkedIn, Uber, Signal, Viber, Netflix, Airbnb, Discord and Claude.

Availability is live rather than fixed: the same service can be well stocked at one hour and short later on. Read it from the API or the dashboard before each order instead of hard-coding a list into your test plan.

How does the Mozambique OTP API flow work end to end?

For developers, the integration is a short sequence against https://otproute.com/api/v1, signed with a Bearer key that begins or_live_:

1. Resolve the Mozambique id (mz) and the service id from GET /api/v1/countries and GET /api/v1/services.
2. Check GET /api/v1/prices?country=mz&service=<id> for the live price and whether numbers are on hand.
3. Send POST /api/v1/activations with {"service": "telegram", "country": "mz"} and keep the returned activation id and number.
4. Collect the code when activation.sms_received hits your endpoint, or query GET /api/v1/activations/{id} every few seconds.
5. Call POST /api/v1/activations/{id}/cancel if the test is abandoned.

Webhook requests carry an X-OTPRoute-Signature header (t=<unix>,v1=<hex>), an HMAC-SHA256 of <t>.<raw body> keyed with your endpoint secret. Verify it, refuse old timestamps, and make the handler idempotent on the activation id. Keys live in the Developer console (up to 10, plus 5 webhook endpoints), and the rate limit is 300 requests per minute. The OTP API integration guide shows the same SMS verification API flow with error handling.

Can a non-developer order a +258 number from the dashboard?

Yes, and it uses exactly the same OTP routing as the API. After you create an account with email and a 6-digit code (or Google), add funds, open the OTP Gateway, choose Mozambique and the service, and confirm the price shown. The number appears at once; paste it into the app, and the code is displayed on the same page when it lands. Two-factor sign-in with an authenticator app is available for the account itself.

Why didn't the code arrive, and what should we try next?

Every activation has a 20-minute window. If it closes without an SMS, or you cancel, the whole amount is credited back to the wallet automatically; you only pay when a code arrives.

If a run keeps coming up empty:

• Give the window time. How fast a code shows up depends on the service and the route.
• Check whether that service accepts virtual numbers; some reject them outright.
• Retry after a pause, or pick another route when the test does not require a Mozambican number specifically.
• Space out attempts instead of hammering the order endpoint, and record each activation id so failures can be compared.

Is there a permanent Mozambican line, and how is it billed?

No self-serve long-term number exists for Mozambique. Dedicated lines are sold only for the United States and Canada, from $1.95/month. Teams that need an ongoing Mozambican line can email [email protected] to ask; whether it is possible depends on local rules, and it may not be.

Payment runs through one prepaid USD wallet, pay as you go, with no subscription. Card and USDT/USDC stablecoin top-ups are both accepted, each followed by a PDF invoice by email. For building and debugging, a development account can be moved to sandbox on request, so simulated numbers and codes flow through your code without spending anything. See pricing for how rates are shown.

Frequently asked questions

Can I test a Mozambique sign-up flow from outside the country?

Yes. The +258 number comes from the OTP Gateway, so your team can run the test from anywhere and read the code in the dashboard or through the API.

What is the API country id for Mozambique?

Use mz in GET /api/v1/prices and in the body of POST /api/v1/activations.

Do Mozambican numbers need a leading zero?

No. Mozambique has no domestic trunk prefix, so the stored form is simply +258 followed by nine digits.

What does it cost to receive a Mozambique SMS OTP?

Codes start at $0.20 per code, and the exact price for each service is returned live by the API and shown in the dashboard before you order.

Will a +258 test number still work for logging in next week?

Plan on it not working. An OTP Gateway number is for one code, and long-term dedicated numbers are offered only in the US and Canada.

Are there rules on what we can verify with these numbers?

Yes. Use them only for testing and operating your own legitimate products and accounts, follow each service's terms, and stay within OTP Route's 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.