Receiving Georgian +995 SMS codes for QA and regional launches

Why does the country of Georgia trip up test plans?

The first surprise is the name. Georgia the country shares it with a US state, so form libraries, analytics filters and even teammates mix the two up. In the API the country id is ge, matching ISO code GE, and the dial code is +995. A test that silently picks a US +1 number because someone typed "Georgia" into a search box is a bug worth catching early.

The second is the script. Georgian uses its own alphabet, Mkhedruli, which sits outside the GSM 7-bit character set. Any SMS containing Georgian letters is sent as Unicode, so each segment holds fewer characters and longer messages split sooner. If your own product sends Georgian-language messages, that is exactly what localisation QA should look at.

What does a correctly stored +995 number look like?

Inside the country, people dial a 0 trunk prefix before the subscriber number; internationally that 0 disappears. Mobile numbers are nine digits and begin with 5, so the E.164 form is +995 followed by nine digits beginning with 5.

A practical normalisation routine for Georgian input:

• Remove spaces, dots and dashes that users type out of habit.
• If the value starts with 0 and has ten digits, drop the 0 and add +995.
• If it starts with 995 and no plus sign, add the plus.
• Reject anything that still is not twelve digits after the plus.

Storing one canonical format means the number your test enters matches the number your backend later looks up.

Which Georgian verification flows can I exercise?

The Georgia snapshot currently shows WhatsApp, Telegram, Google (Gmail & YouTube), Facebook, Instagram, TikTok, X (Twitter), ChatGPT (OpenAI), Claude, Microsoft & Outlook, Discord, LinkedIn and Viber, and the full catalogue runs to more than 1,500 services.

Teams test here for a few recurring reasons: a product entering the South Caucasus, a remote team in Tbilisi verifying regional business accounts, or a localisation pass that checks Georgian text renders properly on sign-up screens. Availability shifts through the day, so before you reserve a +995 number for testing, ask the API rather than trusting yesterday's list. OTP routing picks from what is live at that moment.

How does the Georgia OTP API call sequence run?

All calls go to https://otproute.com/api/v1 with a Bearer key prefixed or_live_. Each account can hold up to 10 keys, which lets staging and production stay separate.

1. Fetch GET /api/v1/countries once and confirm the id ge.
2. Call GET /api/v1/prices?country=ge&service=<id> to read today's price and availability.
3. Place the order with POST /api/v1/activations, for example {"service": "whatsapp", "country": "ge"}.
4. Enter the +995 number in the app under test and trigger its SMS step.
5. Read the code from GET /api/v1/activations/{id}, or let a webhook deliver it.
6. If the scenario aborts, release the order with POST /api/v1/activations/{id}/cancel.

The rate limit of 300 requests per minute leaves room for polling every few seconds across several parallel jobs.

Should I poll or use webhooks for +995 codes?

Both styles use the same SMS verification API, and polling is fine for a single developer who wants to receive Georgia SMS OTP messages from a laptop. In CI, a webhook is calmer: register up to 5 endpoints in the Developer console and subscribe to activation.sms_received, activation.expired and activation.cancelled.

Verify every request. The X-OTPRoute-Signature header carries t=<unix>,v1=<hex>; compute HMAC-SHA256 of <t>.<raw body> with the endpoint secret, compare in constant time, and drop requests whose timestamp is old. Store results keyed on the activation id so a repeated delivery is harmless. The webhook capture write-up has a worked pattern.

A Georgian code did not arrive. What should I try?

First, give it the full 20 minutes; the order refunds itself if nothing comes. Then consider whether the service accepts virtual numbers for Georgian accounts at all, since some do not. Retrying later, or running the same test through another service route, often clears a temporary dip. What you should not do is fire new orders in a tight loop, which burns time and looks suspicious to the receiving platform.

Long-term numbers, billing and a sandbox

OTP Route does not sell self-serve long-term Georgian numbers. Dedicated lines exist only in the United States and Canada, from $1.95/month; to ask about a persistent +995 line, write to [email protected], and the answer will depend on local rules.

The wallet is prepaid in USD with no subscription: top up by card or USDT/USDC and receive a PDF invoice each time. A sandbox account, available on request, returns simulated numbers and codes for integration tests. See pricing or create an account to start.

Frequently asked questions

How do I make sure I get a number from Georgia the country, not the US state?

Use the country id ge in API calls and look for the +995 dial code in the dashboard. A US state never has its own country id.

Can I test a Georgian sign-up flow without a local SIM card?

Yes. An OTP Gateway number with the +995 prefix receives the code, and you read it in the dashboard or through the API.

Do I keep the leading 0 when saving Georgian mobile numbers?

No. The 0 is a domestic trunk prefix; store the number as +995 plus nine digits starting with 5.

Why do Georgian-language SMS messages look shorter per segment?

Georgian letters fall outside the GSM 7-bit alphabet, so the message uses Unicode encoding, which fits fewer characters into each segment.

What is the price of a Georgian verification number?

It starts at $0.20 per code and depends on the service. The live price comes from GET /api/v1/prices and appears in the dashboard before you order.

Am I charged if the platform rejects the number?

No. When no SMS arrives within the 20-minute window, or you cancel, the full amount goes back to your wallet.

What uses are allowed with +995 numbers?

Testing your own product, QA automation and operating your own business accounts. Follow each service's terms and the OTP Route Acceptable Use Policy.

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.