Automating +260 SMS verification for Zambian sign-up tests

Which endpoints does a Zambia OTP API integration call?

Integration is a short chain of HTTPS calls to https://otproute.com/api/v1, each carrying Authorization: Bearer with a key prefixed or_live_. Zambia's country id is zm.

• GET /api/v1/countries and GET /api/v1/services: reference data, fine to cache for a day.
• GET /api/v1/prices?country=zm&service=<id>: live price plus whether that route can take an order right now.
• POST /api/v1/activations with {"service": "whatsapp", "country": "zm"}: returns the activation id and a +260 number.
• GET /api/v1/activations/{id}: status and, once received, the code.
• POST /api/v1/activations/{id}/cancel: give the number back early.
• GET /api/v1/balance: run it first so a test suite stops quickly on an empty wallet.

Generate keys in the Developer console, up to 10 per account, one per environment is a tidy pattern. The account limit is 300 requests per minute. Full schemas sit in the API docs.

How should the webhook receiving +260 codes be written?

Polling works, but once several activations run at once a webhook is cleaner. Add up to 5 endpoints in the Developer console and subscribe to activation.sms_received, activation.expired and activation.cancelled.

Each request carries X-OTPRoute-Signature: t=<unix>,v1=<hex>. Build the string <t>.<raw body>, compute HMAC-SHA256 with the endpoint's secret and compare against v1 in constant time. Use the raw bytes as received, refuse timestamps that are more than a few minutes old, and store results keyed on the activation id so a retried delivery changes nothing. Respond with a 2xx quickly and do the slow work afterwards. Our walkthrough on securing OTP webhooks with HMAC has more detail, and SMS OTP testing in CI pipelines shows where this fits in a build.

What services can a Zambia verification number receive codes from?

The live snapshot puts Zambia at more than 1,100 services. Among them: WhatsApp, Facebook, Google (Gmail & YouTube), Telegram, Instagram, TikTok, X (Twitter), LinkedIn, Uber, imo, Microsoft & Outlook, Amazon and Netflix. Because routes change hour by hour, let the prices endpoint tell your code what is open before ordering.

Zambian number format and the languages codes arrive in

Zambian numbers are dialed domestically with a trunk 0, then nine digits. In international form the zero goes away, giving +260 followed by nine digits. Normalise everything to that E.164 form before saving, and make sure your input field accepts both the local style users actually type and the international one.

English is the official language, and languages such as Bemba, Nyanja, Tonga and Lozi are widely spoken. Verification SMS normally arrives in English, which keeps parsing simple, but still match on digits so a wording change by the sender does not break your tests.

Teams test on Zambia when they expand into Southern Africa, build onboarding for mobile-money or lending products, or support customers from a regional operations centre. The fintech onboarding page covers that scenario.

Can the same thing be done from the dashboard?

Yes, and it is handy for one-off checks. Log in, open the OTP Gateway, choose the service and Zambia, look at the displayed price, and order. Enter the +260 number in the app; the code appears in the dashboard when it arrives. Cancel an activation you no longer want and its amount returns to the wallet.

What if the code doesn't arrive, and when is a dedicated line better?

Activations last 20 minutes and you pay only when the code arrives. If the window expires or you cancel, the full amount goes back automatically. Some services decline virtual numbers, which is the reason for the refund. When a +260 code is slow: wait out the window, try again later or with another service route, check that the service accepts virtual numbers, and avoid re-ordering in a tight loop.

For an account that must log in again or recover access later, a one-time number is the wrong tool. Dedicated Virtual Numbers fill that role, but only in the United States and Canada, from $1.95/month. OTP Route has no self-serve long-term Zambian line; if you have a real need, write to [email protected], bearing in mind that local rules decide and nothing is assured.

Use numbers only for your own legitimate products and accounts, follow each service's terms, and remember that OTP Route's Acceptable Use Policy applies.

How is a Zambia integration billed and tested safely?

One prepaid USD wallet funds everything; there is no monthly fee and no plan. Top up by card or USDT/USDC and receive a PDF invoice by email each time. While building, request sandbox mode for your development account: simulated numbers and codes let you rehearse the full OTP routing path without wallet spend. Current rates are on the pricing page.

Frequently asked questions

What country id does OTP Route use for Zambia?

zm, as in POST /api/v1/activations with {"service": "telegram", "country": "zm"}.

Can I receive Zambia SMS OTP codes without a Zambian SIM card?

Yes. The OTP Gateway provides a +260 number for testing, and the code reaches you in the dashboard, by webhook or through polling.

How do I store +260 numbers correctly?

Drop the domestic trunk 0 and save +260 plus nine digits in E.164. Format for display separately.

Is the money refunded if WhatsApp or another service rejects the number?

Yes. When no code arrives within 20 minutes, or you cancel, the amount is credited back to your wallet automatically.

Can I keep a Zambian number for future logins?

Not self-serve. Long-term numbers are a US and Canada product; email [email protected] to ask about Zambia, with no promise.

Can I try the integration before paying for real codes?

Yes. Ask for sandbox mode on a development account to get simulated numbers and codes for end-to-end tests.

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.