Does MiniMoth support WhatsApp OTP outside India?

Yes. Every MiniMoth project can send OTPs over WhatsApp to US and EU-area phone numbers, in addition to Indian (+91) numbers. It's opt-in per region — nothing outside India is enabled by default — and uses the same POST /v1/otp/send and POST /v1/otp/verify endpoints already used for domestic OTPs.

Which countries are supported for international WhatsApp OTP?

United States, Canada, United Kingdom, France, Netherlands, Germany, Spain, Italy, Poland, Hungary, Romania, and the rest of Western and Central & Eastern Europe. Each region is enabled and priced separately from your project's dashboard.

Is there SMS fallback for international OTPs?

No. Domestic (+91) sends try WhatsApp first and fall back to SMS automatically if delivery fails. International sends are WhatsApp-only — there's no SMS route for these numbers — so a delivery failure returns an error and refunds the charge instead of retrying over a different channel.

How is international WhatsApp OTP billed?

Per region, at a rate shown in your project's dashboard before you enable it. If your project has its own connected WhatsApp Business Account, every international send is billed at a flat facilitation fee instead, regardless of region.

Do I need to change my integration code to support international numbers?

No. Pass an international phone number in E.164 format to the same otp/send and otp/verify calls you already use — nothing about the request or response shape changes, other than needing to enable the number's region first.

International WhatsApp OTP: Sending OTPs to US and EU Phone Numbers

26 September 2026

If your product has users outside India, you’ve probably hit the same wall: MiniMoth’s OTP API only ever accepted Indian (+91) phone numbers. That’s no longer the case. Every MiniMoth project can now send OTPs over WhatsApp to US and EU-area phone numbers too, opt-in per region, without switching providers or adding a second integration.

What is international WhatsApp OTP?

International WhatsApp OTP is WhatsApp-based one-time-passcode delivery for phone numbers outside India — specifically the United States, Canada, and a defined set of European markets. It works through the exact same POST /v1/otp/send and POST /v1/otp/verify endpoints you already call for domestic (+91) numbers. Pass an international number in E.164 format instead of an Indian one, and MiniMoth handles the rest — no new endpoint, no separate SDK method, no second API key.

Nothing is enabled by default. Each supported region has to be turned on explicitly, per project, before MiniMoth will send to a number in that region.

Which regions are supported?

International WhatsApp OTP currently covers:

United States / Canada
United Kingdom
France
Netherlands
Germany
Spain
Italy
Poland
Hungary
Romania
Rest of Western Europe
Rest of Central & Eastern Europe

Each region is billed separately, and the current rate for every region is shown in your project’s International WhatsApp OTP card in the dashboard before you enable it.

How do you enable it?

Open a project in your MiniMoth dashboard and find the International WhatsApp OTP card on the project details page. Turning on a region there is what lets otp/send accept phone numbers from it — attempting to send to a number in a region you haven’t enabled returns a 403 REGION_NOT_ENABLED error instead of dispatching an OTP, so a stray or unexpected number never results in a surprise charge.

What happens if a WhatsApp send fails? (No SMS fallback)

Domestic (+91) OTPs try WhatsApp first and fall back to SMS automatically if delivery fails — that’s still true for India. International numbers don’t have that fallback: there’s no SMS route for a US or EU number in MiniMoth today, so a WhatsApp delivery failure surfaces directly as a 502 INTERNATIONAL_WHATSAPP_FAILED response, and the charge for that attempt is refunded to your wallet automatically. No action is needed on your end beyond handling the error like any other failed send.

If a number keeps failing to deliver in a short window, further sends to it return 502 INTERNATIONAL_WHATSAPP_BLOCKED instead of retrying — no charge is made for a blocked attempt, since nothing was actually sent. The block clears on its own once the window passes without a new failure.

How is it billed?

Each enabled region has its own per-OTP rate, shown in the dashboard before you turn it on, so there’s no surprise cost when you opt in. If your project has its own connected WhatsApp Business Account instead of using MiniMoth’s shared one, every international send — regardless of which region the number is in — is billed at a flat facilitation fee. See Pricing for current rates, and Branded WhatsApp OTP for connecting your own account.

Do you have to enable it?

No. International WhatsApp OTP is entirely opt-in, region by region, project by project. If all of your users are in India, nothing about your existing integration changes. If you’re expanding to the US or Europe, turning on the regions you need takes one toggle per region in your project’s dashboard — see the International WhatsApp OTP docs for the full integration details.