Montenegro (+382) Verification Numbers for Product and QA Teams

Why would a team add Montenegro to its test matrix?

Montenegro is a small Adriatic market, but it shows up in plenty of roadmaps. Products launching across the Western Balkans usually ship it together with Serbia, Bosnia and Herzegovina and Croatia, because the languages are closely related and one localisation effort can cover several countries. Travel, booking and ride apps care about the coastal holiday season, and companies with Montenegrin customers abroad want to see what a +382 user experiences at sign-up.

Montenegrin is the official language, while Serbian, Bosnian, Albanian and Croatian are also in official use, and text may appear in Latin or Cyrillic script. A Montenegro verification number lets QA confirm that the phone step behaves correctly before real users meet it.

How are +382 mobile numbers written, and how should you store them?

Domestically, Montenegrin numbers carry a trunk prefix of 0, and mobile numbers are dialed as 06x followed by six more digits. The national number after the 0 is eight digits long. To build the E.164 form, drop the 0 and prepend the country code, so a local 06x xxx xxx becomes +3826x xxx xxx (stored without spaces).

Practical rules for your own systems:

• Accept input with or without the 0 and normalise before saving.
• Store only the canonical +382… string; format for display at the edge.
• Do not hardcode mobile prefixes as a validity check, because numbering ranges can be reassigned and users port between networks.

What language will Montenegrin OTP messages use?

Most global apps send codes in English or in the language the user picked in the app. Where a service localises for the region, expect Latin-script Montenegrin or Serbian, and occasionally Cyrillic, which is sent as Unicode SMS. Your extraction logic should look for the digit sequence rather than a fixed phrase, so a template change on the sender's side does not break a passing test.

Which services are available on the `me` route?

The current snapshot lists more than 1,400 services for Montenegro. Frequently used ones include Viber, which is widely used across the Western Balkans, plus WhatsApp, Telegram, Instagram, Facebook, Google (Gmail & YouTube), TikTok, Snapchat, Signal, LinkedIn, Discord, Amazon, Airbnb and Uber.

What is offered at a given minute comes from our carrier partners and shifts during the day, so fetch the live list from GET /api/v1/services or check the dashboard rather than caching it for long.

How do I receive Montenegro OTPs through the SMS verification API?

Create a Bearer key (prefix or_live_) in the Developer console, then:

1. Read the current price with GET /api/v1/prices?country=me&service=<id>.
2. Order with POST /api/v1/activations and a body like {"service": "viber", "country": "me"}.
3. Receive the activation.sms_received event on your webhook, or poll GET /api/v1/activations/{id} at a modest interval.
4. Cancel unused orders with POST /api/v1/activations/{id}/cancel.

Check the X-OTPRoute-Signature header on every delivery: compute HMAC-SHA256 over the timestamp, a dot and the raw body using the endpoint secret, compare, and discard old timestamps. Key your handler on the activation id so a retried delivery is processed once. The HMAC webhook guide and the API docs have the details; accounts get up to 10 keys, 5 webhook endpoints and 300 requests per minute.

What is the dashboard path, and what if no code arrives?

Non-developers can get a +382 number for testing by picking Montenegro and a service in the dashboard, review the price, order, and watch the code appear next to the +382 number.

Each activation lasts 20 minutes. You pay only if the code arrives; when the window expires empty or you cancel, the full amount returns to the wallet. If a code is missing, give the window its full time, confirm the service accepts virtual numbers, and retry later or with another service route instead of reordering in a rapid loop.

Can I keep a Montenegrin number, and how do payments work?

There is no self-serve long-term +382 line. Dedicated Numbers exist only in the United States and Canada, from $1.95/month; for a lasting Montenegrin number you can email [email protected], though availability depends on local regulation.

OTP Route runs on a prepaid USD wallet with no subscription. Top up by card or USDT/USDC and receive a PDF invoice for every top-up. Ask for sandbox mode on a development account to test end to end with simulated numbers. Use numbers only for your own products and accounts, respect each service's terms, and remember that the Acceptable Use Policy applies.

Frequently asked questions

Can I receive a +382 code without a Montenegrin SIM card?

Yes. The OTP Gateway issues a Montenegro number for one verification, and the code appears in your dashboard or reaches your systems through the API.

Should I store Montenegrin numbers with the leading 0?

No. The 0 is a domestic trunk prefix; save the E.164 form beginning with +382 and add the 0 back only for local display if you need it.

What is the country id for Montenegro in the API?

It is me, used in the prices query and in the activation request body.

How much does a Montenegro verification number cost?

It starts from $0.20 per code, and the figure for a given Montenegrin service comes back from the prices endpoint, so a script can check it before every order.

Is a +382 order refunded when Viber or another app sends nothing?

It is returned in full to your wallet when the 20-minute window ends without an SMS, or as soon as you cancel.

Can I test Cyrillic-script OTP messages with a Montenegro number?

Only if the service you are testing chooses to send Cyrillic text; the content is set by the sender. Build your parser to extract digits from any script.

Is OTP routing for Montenegro available inside CI pipelines?

Yes. Many teams order through the API from their test runner; see OTP testing in CI for patterns that avoid flaky retries.

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.