Testing Norwegian phone verification on real +47 routes

What makes Norwegian phone numbers easy, and where do validators trip?

Norway is one of the friendlier markets for phone-field logic. There is no trunk prefix: a number is eight digits whether dialed at home or abroad, and international form simply adds +47 in front. Mobile numbers typically begin with 4 or 9. So the E.164 string is +47 followed by eight digits, nothing removed.

Typical bugs come from elsewhere. Validators written with a ten-digit assumption reject valid Norwegian input, and some sign-up forms insist on a leading zero that Norwegian users never type. Include an eight-digit +47 case in your test matrix and you will catch both.

Language, characters and privacy on the Norwegian market

The official languages are Norwegian, in its Bokmål and Nynorsk written forms, and Sami. Many services send verification messages in Norwegian or English depending on the account locale. Norwegian text uses æ, ø and å, so check that your verification screen and any copy around the code render those letters properly, and extract the code by matching digits.

Norway belongs to the European Economic Area, so GDPR applies to personal data your QA environment collects, including the phone numbers and message bodies in logs. Keeping test numbers separate from staff phones is a sensible part of that hygiene; our page on privacy-first sign-ups expands on it.

Teams usually verify on Norway when they launch across the Nordics, localise an app into Norwegian, or support Scandinavian customers from a regional operations hub.

Which services can you verify with a Norway verification number?

Norway has more than 1,500 services in the current snapshot. Popular ones include Google (Gmail & YouTube), Microsoft & Outlook, LinkedIn, Signal, WhatsApp, Telegram, Facebook, Snapchat, Airbnb, Uber, Netflix, Amazon, Discord and ChatGPT (OpenAI). Because availability shifts during the day, request the live list before every run.

How do you call the Norway OTP API from a test suite?

Authenticate against https://otproute.com/api/v1 with a Bearer key that starts with or_live_; keys are issued in the Developer console, up to 10 per account. Norway's country id is no, which is worth quoting in configuration files so nobody mistakes it for a boolean.

1. Resolve the service id once through GET /api/v1/services.
2. Call GET /api/v1/prices?country=no&service=<id> for the live price and whether the route is open.
3. Send POST /api/v1/activations with {"service": "signal", "country": "no"} and keep the activation id.
4. Enter the +47 number in your own sign-up or login form.
5. Read the code from GET /api/v1/activations/{id}, or let a webhook tell you.

For webhooks, register up to 5 endpoints and handle activation.sms_received, activation.expired and activation.cancelled. Verify X-OTPRoute-Signature by computing HMAC-SHA256 of <t>.<raw body> with the endpoint secret, refuse old timestamps, and treat a repeat delivery for the same activation id as a no-op. The rate limit is 300 requests per minute. The webhook-based OTP capture article shows the handler pattern.

Is there a dashboard route for colleagues who don't code?

Yes. In the dashboard, open the OTP Gateway, pick a service, select Norway, read the price, and order. A +47 number appears; enter it in the app, and the code is displayed in the same view once received. Cancelling an activation you no longer need returns the money to the wallet.

Gateway or dedicated line: what if the Norwegian account must log in again?

The OTP Gateway gives one code per number. If an account needs the same number for future logins or recovery, the answer is a Dedicated Virtual Number, but that product exists only for the United States and Canada, from $1.95/month. OTP Route has no self-serve long-term line for Norway. Teams with a genuine need can email [email protected]; whether anything is possible depends on local rules. The virtual numbers page describes what the US/Canada lines include.

Troubleshooting a missing +47 code, plus billing

Every activation has a 20-minute window, and you pay only if the code arrives. An empty window or a cancel puts the full amount back in the wallet without a ticket. If a code is late, wait out the window, try later or through a different service route, check that the service takes virtual numbers, and avoid hammering the order endpoint. Use the numbers for your own legitimate accounts and products, follow each service's terms, and note that OTP Route's Acceptable Use Policy applies.

Funding is pay as you go from one USD wallet, topped up by card or USDT/USDC, with a PDF invoice for every top-up and no monthly fee. A sandbox mode, available on request for development accounts, simulates numbers and codes for free integration testing. Details are on the pricing page.

Frequently asked questions

Do Norwegian numbers need a leading zero?

No. Norway has no trunk prefix, so the eight digits stay the same and E.164 just adds +47.

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

Yes. Order a +47 number for testing on the OTP Gateway, enter it in the form, and collect the code via dashboard, API or webhook, from $0.20 per code.

What is the API country id for Norway?

no. Quote it as a string in YAML or similar config formats so it is not parsed as false.

Can OTP Route give me a Norwegian number I keep?

Not self-serve. Long-term Dedicated Numbers cover only the US and Canada; email [email protected] if you need to ask about Norway.

What happens to my money if the SMS never arrives?

It is returned. With no code after 20 minutes, or after you cancel, the wallet is credited the full amount automatically.

Will codes arrive in Norwegian?

Sometimes. Many services pick Norwegian or English from the account settings, so build your parser around the digits.

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.