Skip to main content
June 22, 2026 · By Piyush Sahoo · Updated November 3, 2026 An E.164 phone number is the full international form of a phone number: a country code plus the national number, at most 15 digits, with no spaces or domestic prefixes. APIs usually write it after a plus sign, so an Indian mobile becomes +91 followed by its ten digits, run together. This guide covers what the February 2026 edition of the standard says, how each Indian number series converts, which checks you need, and where the format breaks inside a real stack.
Key takeaways
  • E.164 has a 15-digit ceiling. It counts the country code and national number, and it excludes the plus sign and every dialling prefix.
  • The plus is a marker. ITU-T treats it as a symbol, while most APIs require it, so you need one stored convention.
  • India has its own traps. A ten-digit mobile can begin with 91, and a local landline number can’t be converted without its STD code.
  • Valid format isn’t permission. A correct +91 number can still be unallocated, or be the wrong series for your call under TRAI rules.
  • Normalise in one place. Do it once on the way in, and again on webhooks (callbacks) that return digits in a different form.

What is an E.164 phone number?

E.164 is an ITU-T recommendation titled “The international public telecommunication numbering plan”. The edition in force is dated February 2026. The first issue dates from 1984, and the older E.163 plan was merged into it in 1991. The name is a document number, not an acronym. Developers use it as shorthand for one thing the plan makes possible: a single spelling of a number that reads the same from any country. The standard covers more than ordinary phone lines. Its current edition defines eight categories, including Geographic Areas, Global Services, Networks, and IoT and M2M services. Almost everything you dial sits in the geographic category, which is what the rest of this guide describes.

How is an E.164 number structured?

A geographic E.164 number has two fields. The country code runs from 1 to 3 digits, and the national (significant) number can use up to 15 minus that length. Countries may divide the national part further, usually into a national destination code and subscriber number, and that split is their own decision. Stacked bar chart of digits used against the ITU limit of 15. Universal Freephone and US or Canada numbers use 11 digits, UK London and Indian mobile or fixed numbers use 12, and the longest Indian 1800 numbers and Indian M2M SIM numbers both reach 15. Stacked bar chart of digits used against the ITU limit of 15. Universal Freephone and US or Canada numbers use 11 digits, UK London and Indian mobile or fixed numbers use 12, and the longest Indian 1800 numbers and Indian M2M SIM numbers both reach 15. The chart shows why a shared length rule is safer than a per-country guess. Universal Freephone numbers have a fixed 11 digits, and India’s everyday numbers leave three digits spare, yet TRAI describes toll-free formats of up to 13 digits and a 13-digit series for SIM-based M2M devices. Add the two digits of +91 and both land exactly on the limit, so test your schema against them. Some things travel with a number without being part of it. A quicker test is to ask what each one depends on: The plus deserves a clear answer, because sources seem to disagree. The ITU text treats it as a symbol. Many telephony APIs list it as a requirement, and RFC 3966 builds it into its global-number syntax. Both views hold: the digits are the number, and the plus is the convention software uses to mark them as complete.

How do you write a number in E.164?

Start from the country, because the conversion isn’t the same everywhere. These examples use masked digits, and the UK row sits in a range Ofcom sets aside for drama. The last two rows are why “delete the first zero” is a bug. libphonenumber’s list of false assumptions records that Italy fixed its zero into numbers in 1998, and that Argentine mobiles change digits in the middle between national and international form. We confirmed the Italian rule by parsing a synthetic number with the library’s Python port.

How do Indian numbers map to E.164?

The country code is the easy part. Ambiguity comes from everything people type around it. Run this rule stack when you already believe the input is Indian, such as a form with India selected. Rule stack for normalising Indian input, read top to bottom. Plus or 00: swap to plus and drop a 0 after 91. 1800 with 8 to 13 digits: add plus 91 and flag as domestic-only. Exactly 10 digits, even starting 91: add plus 91. 11 digits starting 0: replace the 0 with plus 91. 12 digits starting 91: add plus. 13 digits starting 575 from an M2M source: add plus 91. Anything else, including 6 to 8 digits: stop and do not guess. Rule stack for normalising Indian input, read top to bottom. Plus or 00: swap to plus and drop a 0 after 91. 1800 with 8 to 13 digits: add plus 91 and flag as domestic-only. Exactly 10 digits, even starting 91: add plus 91. 11 digits starting 0: replace the 0 with plus 91. 12 digits starting 91: add plus. 13 digits starting 575 from an M2M source: add plus 91. Anything else, including 6 to 8 digits: stop and do not guess. Three of those rules prevent the costliest mistakes:

What each Indian series looks like

We ran synthetic numbers through phonenumbers 9.0.42, a Python port of libphonenumber, on November 3, 2026. Digits are masked here. Treat the “Library result” column as one version’s behaviour, not a regulation. Metadata changes as plans change, so re-run your own checks after upgrades. One planned change makes the case for E.164 neatly. TRAI recommended in February 2025 that all fixed-line calls be dialled as 0 plus SDCA code plus subscriber number. We could not confirm whether DoT has adopted it. Either way, it changes how people dial and not the digits after +91, so numbers stored in E.164 wouldn’t need rewriting.

How do you validate an E.164 number?

Validation isn’t one check. Each layer answers a different question, and passing one tells you nothing about the next. These four layers give you checks you can run. Staircase of four validation layers. Shape asks whether it could be E.164 and catches spaces, plus zero, and a 16th digit. Numbering plan asks whether it fits the country and catches wrong lengths and unused ranges. Network asks whether it exists now and catches unallocated numbers. Permission asks whether you may call it from this number and covers consent, series rules, caller ID, and geo settings. Staircase of four validation layers. Shape asks whether it could be E.164 and catches spaces, plus zero, and a 16th digit. Numbering plan asks whether it fits the country and catches wrong lengths and unused ranges. Network asks whether it exists now and catches unallocated numbers. Permission asks whether you may call it from this number and covers consent, series rules, caller ID, and geo settings. Shape is the regular expression most guides stop at: a plus, a first digit from 1 to 9, and up to 14 more digits. The first digit can’t be 0 because no country code begins with it. A pattern can’t prove a number is real. In our test, a +91 number one digit short passed this layer without trouble. Numbering plan needs country metadata. libphonenumber offers isPossibleNumber, a quick length-based guess, and isValidNumber, which checks against the country’s ranges. It’s also used by the Android framework. In our test, isPossibleNumber accepted several Indian strings that isValidNumber rejected, so don’t treat the two as equal. Network tells you what’s true today. Numbers get disconnected, recycled, and reassigned, so that same list advises against storing validity or line type. Re-check them when you need them. Permission sits outside numbering entirely. In India, TRAI assigns 1600xx to service and transaction calls by BFSI and government entities, and 140xx to promotional calls. A flawless E.164 string on the wrong series is still the wrong call. Check the Indian calling regulations and take legal advice for your own case.

Which checks do you need?

Testing has its own rule: never put a stranger’s number in fixtures. Use reserved ranges such as the Ofcom block above, and masked placeholders in documentation.

Where does E.164 break in a real stack?

Keep one canonical form, normalised once at the boundary. The harder part is knowing where the boundaries are. Most failures happen when a system re-encodes the number or receives it from someone with a different convention. Three lanes showing one masked number. Capture and store: a web form holds the typed local form, a normaliser produces plus 91 form, and the database stores it. Send: a JSON body keeps the plus, a URL path encodes it as percent 2B, and SIP carries it in the user part with user equals phone. Receive: an answer webhook gives From with a plus to check after decoding, a WhatsApp webhook gives digits without a plus, and both pass through the same normaliser. Three lanes showing one masked number. Capture and store: a web form holds the typed local form, a normaliser produces plus 91 form, and the database stores it. Send: a JSON body keeps the plus, a URL path encodes it as percent 2B, and SIP carries it in the user part with user equals phone. Receive: an answer webhook gives From with a plus to check after decoding, a WhatsApp webhook gives digits without a plus, and both pass through the same normaliser. That last row explains a puzzle many developers hit. Digits-only values aren’t always a bug. They can reflect what networks and some messaging platforms carry, so your code needs to add the plus back before it compares two numbers. Length deserves similar care. A text column of 16 characters holds the plus and 15 digits. However, libphonenumber reports German numbers beyond 15 digits, and ITU-T says numbers over the limit aren’t international E.164 numbers. Keep the normalised column tight and the raw column generous.

E.164 vs other number formats

These names cover different jobs, so choose by what will read the value next. The table sorts them by job, using one UK number. Don’t confuse any of these with the E.212 identity a mobile network uses for a subscription. It’s also a long digit string attached to a SIM, but it’s a separate identifier. A number also tells you little about whoever holds it. One number can be shared, and a country code doesn’t reveal where someone lives. Think of it as an address, and be careful using it as an identity key.

How Vobiz handles E.164

Vobiz uses E.164 across its phone number, voice, messaging, and call record APIs. Here’s where the format appears and what to send.
  • Numbers. Number objects carry an e164 field, and you buy a number by passing its e164. A JSON body keeps the literal +.
  • URL paths. Endpoints such as /numbers/{e164} need the plus encoded as %2B, as the Release a Phone Number reference specifies.
  • Inventory filters. When you browse inventory, search matches a substring of the E.164 number. exclude takes prefixes with the country code, and the leading + is optional there.
  • VobizXML. <Number> inside <Dial> and the parent callerId both use E.164, and the docs show them with a plus.
  • Make Call API. The Make Call reference shows from and to as digits with the country code. to also accepts a SIP URI, and < separates up to 1,000 destinations.
  • SMS and WhatsApp. SMS from and to use E.164. WhatsApp sends use a plus in to, while WhatsApp webhooks (callbacks) show wa_id and from as digits only.
  • Integrations. Each guide states its form. Dograh takes your number without the plus, and ElevenLabs takes it with the plus.
  • Records. Call detail records report caller_id_number in E.164, which helps when you join calls to your own contacts.
Because these surfaces show both spellings, keep one form in your database and adapt at each edge. Normalise values from answer URL requests and webhooks before you compare them. When a number fails on a call, the hangup causes reference tells you which layer to fix: For Indian commercial traffic, the 140 and 160 series guide covers how to get these numbers, and Indian calling regulations cover their use. Vobiz is available in 130+ countries. Calls, messages, and number purchases can bill your account or reach real people. Run them only with your own Auth ID and Auth Token, after confirming the exact numbers.

Frequently asked questions

It stands for nothing. E.164 is how ITU-T numbers one of its recommendations, whose title is The international public telecommunication numbering plan. The current edition was approved in February 2026. People use the name for the international number format that the plan defines.
Write +91, then the ten-digit national number, with no spaces and no leading 0. A number dialled locally as 0 followed by ten digits loses that 0. Fixed-line numbers include the STD code in those ten digits, so a local six- to eight-digit number can’t be converted alone.
Strictly, no. ITU-T treats the plus as a symbol showing that an international prefix is needed, and it doesn’t count towards the 15 digits. Many APIs and the tel URI standard still require it, so include it unless the reference for your endpoint shows otherwise.
ITU-T recommends a maximum of 15 digits, including the country code and excluding any prefix. A one-digit country code leaves 14 digits for the national number, and a three-digit code leaves 12. In practice most numbers are shorter, such as 12 digits for an Indian mobile.
Know the country first. Remove separators and any international prefix, drop the trunk prefix where the country treats it as a prefix, then add the plus and country code. Use a metadata-driven library, because rules differ by country. Italy, for example, keeps its leading zero.
Only partly. A pattern confirms the shape: a plus, a non-zero first digit, and at most 15 digits. A string can pass with a country code nobody holds, a wrong length for its country, or a dead line. Add a numbering plan library, then use live signals when reachability matters.

Further reading on Vobiz

Sources

Standards Regulators Software and guides

Build on Vobiz

Provision a number in E.164 format and place your first programmable call.