Picking the right route for Armenian (+374) verification codes

Which OTP Route product suits an Armenian verification job?

Settle this before writing any code, because the answer shapes the whole integration. OTP Route sells two things, and only one of them reaches Armenia.

• OTP Gateway: a number from our carrier partners, reserved for one service and one code. It suits sign-up tests, regression runs against a localized onboarding screen, and one-off verification of a business profile. This is what you use for +374.
• Dedicated Virtual Numbers: a line you keep while it renews, with inbound and outbound SMS plus browser calling. It is sold instantly only for the United States and Canada, from $1.95/month.

There is no self-serve Armenian long-term number. If your project truly needs one, write to [email protected] and describe the use case; whether anything can be arranged depends on local rules, so treat it as a question rather than a plan. For accounts that must keep logging in after the first code, a US or Canadian dedicated line is the practical alternative.

What can a +374 number verify on the OTP Gateway?

Armenian routes currently cover more than 1,700 services. Popular ones in the live snapshot include WhatsApp, Telegram, Viber, Google (Gmail & YouTube), Facebook, Instagram, TikTok, Signal, LinkedIn, Microsoft & Outlook, Discord, ChatGPT (OpenAI) and Uber.

Messengers deserve a note: Viber and Telegram are both familiar names in Armenia, so a product that hands users off to a chat channel there will often want test accounts on them. Availability per service moves during the day, which is why the API returns it live instead of us printing a fixed list.

How does the Armenia OTP API call sequence run?

Everything lives under https://otproute.com/api/v1 with a Bearer key prefixed or_live_ from the Developer console. Armenia's country id is am.

1. Look up service ids once with GET /api/v1/services, and confirm am via GET /api/v1/countries.
2. Ask GET /api/v1/prices?country=am&service=<id> for the current price and whether the route is open.
3. Create the order with POST /api/v1/activations and a body like {"service": "telegram", "country": "am"}. Store the activation id it returns.
4. Put the +374 number into the flow under test, then wait for activation.sms_received on your webhook or poll GET /api/v1/activations/{id}.
5. If the run is aborted, call POST /api/v1/activations/{id}/cancel so the funds return straight away.

Webhook requests carry X-OTPRoute-Signature: t=<unix>,v1=<hex>. Compute HMAC-SHA256 over <t>.<raw body> with the endpoint secret, compare, and discard anything with an old timestamp. The API docs list the remaining events, activation.expired and activation.cancelled, which are keyed on the same activation id. Accounts are limited to 300 requests per minute, so poll gently.

Can a colleague without API access order a +374 number?

Yes. Operations staff and support agents can do the same thing from the browser:

1. Sign in, open the OTP Gateway and choose Armenia.
2. Pick the service; the live price shows before you confirm.
3. Copy the number into the app or site that asks for it.
4. Keep the activation open; the code appears beside the number when it arrives.

The dashboard and the API share one wallet and one order history, so a QA engineer and a support lead can work from the same balance.

How should Armenian numbers be stored, and what language do codes use?

Inside Armenia people dial a leading 0 as the trunk prefix. In international form that 0 disappears and the country code +374 is followed by an eight-digit national number. Normalize every input to E.164 before saving: strip spaces and dashes, drop the domestic 0, and keep the plus sign with 374. A form that accepts the domestic format but stores it untouched will later fail lookups against the E.164 value your test harness holds.

Armenian has its own alphabet, and Russian is widely understood, so an Armenian-language UI is a real localization target. Verification texts from global apps usually follow the app's language setting and often arrive in English, but a localized template can come back in Armenian or Russian script. Extract the digits with a pattern that ignores surrounding words, and make sure logs and databases handle UTF-8 so non-Latin message bodies are not mangled.

Teams test here for practical reasons: localized onboarding for an Armenian launch, support for the large Armenian diaspora signing up from abroad with home numbers, or regional operations that cover the South Caucasus.

What should I check when no Armenian code arrives?

Silence inside the window has a few usual causes, and none of them cost you money.

• The service declined the number. Some platforms refuse virtual numbers outright; that is exactly why unused activations are refunded.
• The route is busy. Let the 20-minute window run its course, then try later or pick a different service route.
• The test resent too quickly. Re-ordering in a tight loop rarely helps and can trip a service's own rate limits. Back off between attempts.

If nothing arrives before the window closes, or you cancel, the full amount returns to your wallet automatically. Our guide to reducing failed OTP deliveries covers retry timing in more depth.

How are Armenian activations billed and tested?

OTP Route runs on one prepaid USD wallet with no monthly fee and no plan to choose. Top up by card or with USDT/USDC stablecoins, and each top-up produces a PDF invoice sent by email. Current rates sit on the pricing page and come back from the prices endpoint.

Before spending real balance, ask for sandbox mode on a development account. It returns simulated numbers and codes, so a CI job can exercise the full am flow end to end. The QA testing overview shows how teams wire that into a pipeline. Use the service only for your own products and legitimate accounts, follow each platform's terms, and note that the OTP Route Acceptable Use Policy applies.

Frequently asked questions

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

Yes. Order a +374 number for your service on the OTP Gateway, enter it in the flow, and read the code in the dashboard or via the API with country id am.

What does a +374 number for testing cost?

Codes start from $0.20 per code, with the exact figure depending on the service. You pay only if the SMS arrives within the 20-minute window.

Should the stored number include the leading 0?

No. Store it in E.164: +374 followed by the eight-digit national number, with the domestic trunk 0 removed.

Can I keep an Armenian verification number for later logins?

Not self-serve. OTP Gateway numbers are for a single code; long-term dedicated lines are a US and Canada product, and you can email [email protected] to ask about other countries.

Will Armenian codes arrive in Armenian script?

Sometimes. Many services send English text, but localized templates may use Armenian or Russian, so parse only the digits and store messages as UTF-8.

Is there a way to test the Armenia integration without spending funds?

Yes. Request sandbox mode for a development account and it will return simulated numbers and codes for the whole activation flow.

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.