Receive New Zealand SMS OTP Codes by API or Dashboard

Temporary +64 number or a long-term line: which do I need?

Picking the right product first saves rework later.

Pick the OTP Gateway when a test or onboarding step needs exactly one code: a fresh QA account, a smoke test of your New Zealand sign-up screen, a check that a Kiwi customer's flow works end to end. You get a number, one code, and the session closes.

Pick a Dedicated Number when the same account must log in again weeks later or a team shares a recovery number. Those long-term lines are offered only in the United States and Canada, from $1.95/month, with inbound SMS forwarded as number.sms_received events.

For New Zealand itself there is no self-serve long-term number. Email [email protected] if your case needs one; the answer depends on local rules and may be no. Calling, outbound SMS and renewal terms for those North American lines are on the virtual numbers page.

Why do product teams test sign-ups in New Zealand?

New Zealand is a common soft-launch market for English-language apps: a smaller audience, a familiar language and an early time zone make it a practical place to watch real onboarding before a wider release. That means the +64 verification step is often the first production path a new market sees, and it deserves its own test cases.

A few things are worth covering:

• Language. English, te reo Māori and New Zealand Sign Language are official. Most services send codes in English, but if your own templates use Māori words with macrons (ā, ō, ū), those characters sit outside GSM-7 and push the SMS into UCS-2, shortening each segment.
• Clock edges. New Zealand is among the first places to reach a new calendar day, so expiry and rate-limit logic keyed on dates can behave differently for local users.
• Market fit. A QA account verified with a local number exercises the same country logic your Kiwi users will hit.

For a release-gate pattern built around checks like these, see our QA testing notes.

How should +64 mobile numbers be stored and normalized?

New Zealand uses a trunk prefix of 0. A mobile number written nationally as 021 123 4567 becomes +64211234567 in E.164: drop the leading 0, then add +64. Mobile ranges begin with 2 once the zero is gone, and their length varies, so never hard-code a single digit count.

Practical rules for your schema:

• Store one canonical E.164 string; format for display only at render time.
• Accept input with spaces, dashes or the trunk zero, then normalize with a maintained phone-number parsing library.
• Add test fixtures for both the national and international spellings, plus a number that a user pasted with +64 and the 0 left in.

Which apps send codes to New Zealand numbers on OTP Route?

The +64 route carries more than 800 services. From the current snapshot, frequently used ones include Google (Gmail & YouTube), WhatsApp, Telegram, Facebook, Instagram, TikTok, ChatGPT (OpenAI), Claude, Microsoft & Outlook, Amazon, Discord, Snapchat, LinkedIn, Uber and Netflix.

Because availability is live, query GET /api/v1/countries and GET /api/v1/services at the start of a run instead of caching a list for weeks. If a service is thin on +64, the neighbouring Australia route is the usual fallback for an English-language comparison.

What does the New Zealand OTP API sequence look like?

Every +64 call goes to https://otproute.com/api/v1 with an or_live_ Bearer key issued in the Developer console. The sequence:

1. Read the live price with GET /api/v1/prices?country=nz&service=uber.
2. Create the activation with POST /api/v1/activations and the body {"service": "uber", "country": "nz"}.
3. Collect the code by polling GET /api/v1/activations/{id}, or let activation.sms_received arrive at your webhook. activation.expired and activation.cancelled tell you when to clean up.
4. Cancel unused orders with POST /api/v1/activations/{id}/cancel, and keep an eye on funds with GET /api/v1/balance.

For webhooks, verify X-OTPRoute-Signature by computing HMAC-SHA256 of <t>.<raw body> with the endpoint secret, reject old timestamps, and make the handler idempotent on the activation id so a retried delivery does no harm. The integration guide has a fuller walkthrough; limits are 300 requests per minute per account.

Can a non-developer order a New Zealand verification number?

Absolutely. In the dashboard, choose New Zealand, pick the service, check the price displayed, and confirm. The +64 number appears on the order; type it into the app, request the SMS, and the code shows up on the same card when it lands. Everything happens inside the 20-minute window, so have the target app open before ordering.

What if the +64 code never shows up?

Give the window its full 20 minutes first, because some senders delay or batch their SMS. If it still stays empty, the service may refuse virtual numbers, or that route may be busy; retry later or test with another service route instead of firing new orders back to back. Unanswered orders, and ones you cancel, are refunded to the wallet automatically. Billing is pay as you go from a prepaid USD wallet: card or USDT/USDC top-ups, a PDF invoice for each, no monthly fee, and sandbox mode on request for dry runs. OTP Route is for your own legitimate accounts and products, under each service's terms and our Acceptable Use Policy.

Frequently asked questions

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

Yes. Order a +64 number on the OTP Gateway, use it in your sign-up form and read the code in the dashboard or through the API.

Do I keep the 0 when saving a New Zealand mobile number?

No. The trunk 0 is dropped in E.164, so 021 123 4567 is stored as +64211234567.

What is the API country id for New Zealand?

It is nz, used in price lookups and in the activation request body.

How much does a New Zealand verification code cost?

Prices start at $0.20 per code and depend on the service; the dashboard and GET /api/v1/prices show the exact figure before you order.

Can I rent a New Zealand number for a few months?

There is no self-serve long-term +64 line. Dedicated Numbers are a US and Canada product, and you can email [email protected] to ask about other countries.

Is polling or a webhook better for collecting +64 codes?

Polling is simpler for a single script; a signed webhook scales better when many test jobs run in parallel. Both return the same code.

Will every app accept a New Zealand OTP Route number?

Not necessarily. Some services reject virtual numbers, which is why an order with no SMS is refunded automatically.

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.