Italian (+39) Verification Numbers for Developers and QA Teams

What makes Italian phone numbers tricky for validators?

Italy breaks a rule many normalisers quietly assume. Elsewhere in Europe you drop the domestic zero when you add the country code, but Italian landlines keep it: a Rome number is written +39 06 … and a Milan number +39 02 …. Mobile numbers start with 3 and are usually ten digits after +39, with no zero in front.

So a library that strips a leading 0 after the country code will corrupt Italian landlines, and a validator that insists on a fixed length can reject valid ones. Store the full E.164 string exactly as +39 plus the national number, and add Italian cases to your phone-parsing tests.

A practical fixture set for Italian QA should hold at least one mobile number, one Rome landline and one Milan landline. Run all three through your parser, your database round trip and any display formatter, and confirm that the stored value is identical to what went in.

Why do teams run verification tests on +39 routes?

Italy is one of the larger EU markets, so it is a common stop when a product expands from one European country to the next. Localisation QA matters too: verification messages here typically arrive in Italian, and your own templates should be checked for accented letters, date formats and copy length. Marketplace, fintech and delivery apps also test Italian onboarding before switching on local payment or courier partners. The fintech onboarding notes cover that pattern.

Operations teams have their own reasons. Agencies that manage Italian clients' social or marketplace profiles prefer to confirm those business accounts on a number that is not an employee's personal phone, and the operations teams page describes how that fits with a shared login.

Which services are on the Italy list?

More than 2,100 services can currently send codes to Italian route numbers. Popular picks include WhatsApp, Instagram, Facebook, Google (Gmail & YouTube), Amazon, eBay, Airbnb, Uber, Telegram, Microsoft & Outlook, LinkedIn, Netflix, Discord and ChatGPT (OpenAI). The list is live, so query it rather than caching it for long.

How does the `it` flow work through the API?

Send requests to https://otproute.com/api/v1 with a Bearer key that begins or_live_. Check the cost with GET /api/v1/prices?country=it&service=<id>, then create the order using POST /api/v1/activations and {"service": "<id>", "country": "it"}. The response gives you an activation id; poll GET /api/v1/activations/{id} or wait for the activation.sms_received webhook, and handle activation.expired or activation.cancelled as the other two endings.

Always verify X-OTPRoute-Signature (HMAC-SHA256 of "<t>.<raw body>") and reject old timestamps; the HMAC guide has the details. Accounts allow 10 keys, 5 webhook endpoints and 300 requests per minute.

In a CI pipeline it is common to order the number in a setup step, run the browser test that triggers the SMS, and then block on a short-lived listener until the webhook arrives or the window closes. Cancel in the teardown step so an aborted run never leaves a number open.

Ordering from the dashboard instead

Non-developers can do the same thing from the web app: open the OTP Gateway, choose the service, choose Italy, confirm the price and copy the +39 number into the app you are testing. The code appears on screen as soon as it arrives. If it does not, wait out the window, confirm the service accepts virtual numbers, then retry later or on another route rather than re-ordering repeatedly.

Keep a note of which service and route you used on each attempt; it makes it much easier to see whether a gap is specific to one app or affects the whole Italian route at that hour.

Is there a permanent Italian line, and how is it billed?

There is no self-serve long-term number for Italy. Dedicated Numbers, from $1.95/month, exist only in the United States and Canada; to ask about an Italian line, write to [email protected], knowing availability depends on local rules. Billing is a prepaid USD wallet topped up by card or USDT/USDC, with PDF invoices and no monthly fee. See pricing or sign up to start, and ask for sandbox mode while you build.

Frequently asked questions

Should I remove the 0 from Italian numbers when adding +39?

Not for landlines: Italian landline numbers keep their leading 0 after +39. Mobile numbers start with 3 and have no zero to begin with.

What is Italy's country id in the OTP Route API?

It is it, used in both the prices query and the activation body.

Can I test an Italian sign-up flow from outside Italy?

Yes. A +39 number from the OTP Gateway receives the code wherever your team sits, and you read it in the dashboard or via the API.

What does an Italy SMS OTP cost?

Italian codes start from $0.20 per code; the API quotes the current rate for each service, and the dashboard displays it before you confirm.

What happens if no Italian code arrives?

After 20 minutes the activation expires and the amount is refunded to your wallet automatically, with no ticket needed.

Can I reuse the same +39 number next month?

No, gateway numbers are for one verification. Long-term lines are only available in the US and Canada.

Will verification messages arrive in Italian?

Often, since many senders localise by country, but some use the account's language setting. Build your parser around the digits rather than the wording.

Are there usage limits I should know about?

Follow each service's terms and OTP Route's Acceptable Use Policy; the gateway is for testing and running your own legitimate products, not for mass account creation.

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.