Liechtenstein OTP API: +423 Codes for QA and Market Launches

What makes a +423 number different from its neighbours?

Liechtenstein runs a closed numbering plan. Subscriber numbers are seven digits long and there is no trunk prefix, so the number a resident dials locally is the same seven digits you append after +423. That is unlike Switzerland and Austria on either side of the border, where a leading 0 has to be stripped before building E.164.

For your database that means one simple rule: store +423 followed by exactly seven digits, and reject anything longer instead of guessing. If your form validation was written for Swiss or Austrian numbers, test it against a +423 input before launch, because length checks copied from those plans will fail.

Why do product teams test in such a small market?

Liechtenstein is a member of the European Economic Area, uses the Swiss franc, and has German as its official language. That combination makes it a useful edge case for a DACH launch: EEA rules on one side, Swiss-style pricing on the other, and German-language copy throughout. Verification templates localized for this market usually arrive in German, although many international services send English text when the account language is set that way.

The country also hosts a sizeable financial and trust sector, so wealth-management and banking apps often need to confirm that their onboarding handles a +423 number end to end. See the QA testing guide for how teams fold country cases like this into a regression suite.

Which services can I verify with a Liechtenstein number?

Today's snapshot for li lists Telegram, Google (Gmail & YouTube), WhatsApp, Facebook, Instagram, Microsoft & Outlook, Amazon, LinkedIn, Signal, Viber, Uber and Airbnb among its popular routes. In total the country covers more than 300 services. Availability changes during the day, so read it live rather than relying on a stored list.

How do I request a +423 code through the SMS verification API?

Every +423 request carries an or_live_ Bearer key and targets https://otproute.com/api/v1.

1. Look up the service id with GET /api/v1/services.
2. Check price and availability with GET /api/v1/prices?country=li&service=<id>.
3. Create the activation: POST /api/v1/activations with {"service": "<id>", "country": "li"}.
4. Receive activation.sms_received on your webhook, verifying X-OTPRoute-Signature (HMAC-SHA256 of <t>.<raw body>) and discarding stale timestamps, or poll GET /api/v1/activations/{id}.
5. Cancel with POST /api/v1/activations/{id}/cancel when a test run ends early.

The integration guide shows the same OTP routing flow with retries and logging.

Can a non-developer order one from the dashboard?

Yes. In the dashboard, open the OTP Gateway, choose Liechtenstein and the service, confirm the displayed price, and paste the number into the app. The code appears on the activation page as soon as it is received, under the same 20-minute window.

This path suits support or compliance staff who need to receive a Liechtenstein SMS OTP once, for instance while confirming that a German-language onboarding screen accepts a seven-digit +423 number for testing, without asking an engineer to write a script for it. The price is visible before you confirm, and the refund rule is identical to the API path, so a failed manual attempt costs nothing.

What should I check when a Liechtenstein code does not arrive?

A missing code costs nothing, because the refund is automatic once the window closes or you cancel. Then work through the usual causes:

• give the activation its full window, since timing depends on the service and route;
• confirm the service accepts virtual numbers at all, as some reject them;
• retry later, or use a nearby route such as Switzerland or Austria if your test allows it;
• never re-order in a tight loop.

Keep every activation tied to your own product or your own business accounts, follow each service's terms, and note that the OTP Route Acceptable Use Policy applies.

Is there a permanent Liechtenstein line, and how do I pay?

Not as a self-serve product. Dedicated Numbers are offered only in the United States and Canada, from $1.95/month; for a long-term +423 line, email [email protected], where availability depends on local rules. Payment runs through a prepaid USD wallet funded by card or USDT/USDC, with a PDF invoice for every top-up. Details are on the pricing page.

Frequently asked questions

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

Yes. The OTP Gateway issues a +423 number for a single code, which you can read in the dashboard or receive by webhook. Pricing starts at $0.20 per code.

Does a Liechtenstein number start with a 0 like Swiss numbers do?

No. Liechtenstein has no trunk prefix, so a number is simply +423 followed by seven digits in both local and international form.

Which country id should my code send for Liechtenstein?

Send li as the country field. Service ids come from GET /api/v1/services.

What language will the verification SMS be in?

German is the official language, so localized templates are usually German. Many global services still send English, depending on how the account's language is set.

Am I charged if the code never arrives?

No. If no SMS reaches the number within 20 minutes, or you cancel, the full amount returns to your wallet automatically.

Can I try the integration without spending money?

Yes. On request, support can switch a development account to sandbox, which returns simulated numbers and codes for end-to-end tests.

How fast does a +423 code arrive?

There is no fixed figure. Delivery depends on the service and the route, which is why the activation stays open for the full window.

Is there a monthly fee for using OTP Route in Liechtenstein?

No. It is pay as you go from a prepaid USD wallet, with no plan to choose, and every top-up gets an emailed PDF invoice.

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.