Phone Number Parse

Choose this endpoint when you need to decompose a phone number into structured fields (country code, national number, region, type) and validate it, especially if you need number type classification (mobile vs landline) or E.164 normalization. Prefer this over a simple regex check when accuracy matters and you need metadata like region or number type. Best for data enrichment, form validation, and pre-flight checks before SMS/voice delivery.

• Invalid or unparseable number returns parsed:false and valid:false with reasons
• Missing default_region for national-format number (without +) causes parse failure
• Malformed input (non-numeric characters) returns an error or invalid result
• Ambiguous number with multiple possible regions returns a list in possibleRegions
• Number within a valid country code but invalid locally returns valid:false with length or pattern reasons