Texau logo

Normalize Phone Number (Utility)

Texau → Normalize Phone Number (Utility)

POST/v1/texau-normalize-phone-number
texau__texau-normalize-phone-numberenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-normalize-phone-number
{
  "mobile_number": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "can_be_internationally_dialed": true,
    "country_code": 1,
    "e164_format": "sample",
    "international_format": "sample",
    "is_possible": true,
    "is_valid": "rec_4f3a91",
    "national_format": "sample",
    "number_type": "sample",
    "region_code": "sample",
    "rfc3966_format": "sample",
    "successfully_parsed": true
  }
}

Normalizes and validates a phone number to E.164, national, and RFC3966 formats with country metadata.

Install

Add normalize phone number (utility) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__texau-normalize-phone-number

When to use this.

The Normalize Phone Number action utilizes TexAu's normalize-phone-number API to standardize and validate phone numbers across multiple formats, including E.164, national, and RFC3966. By inputting a phone number as a text parameter, users can obtain essential metadata such as country code, region, and validity status. The output includes fields like can_be_internationally_dialed (boolean), country_code (countryCode), and various phone formats (e164_format, international_format, national_format, rfc3966_format), along with indicators for validity and parsing success. This action is particularly useful for businesses needing to enrich customer contact data, ensuring accurate communication and compliance with international dialing standards. It falls under the enrichment category, making it ideal for applications in customer relationship management (CRM), marketing automation, and data validation processes.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Normalize Phone Number (Utility)

Try it

The phone number to normalize, as entered by the user.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • can_be_internationally_dialed
    Can Be Internationally Dialed
    nullableboolean
  • country_code
    Country Code
    number
  • e164_format
    E164 Format
    nullabletext
  • international_format
    International Format
    nullabletext
  • is_possible
    Is Possible
    nullableboolean
  • is_valid
    Is Valid
    boolean
  • national_format
    National Format
    nullabletext
  • number_type
    Number Type
    nullabletext
  • region_code
    Region Code
    nullabletext
  • rfc3966_format
    Rfc3966 Format
    nullabletext
  • successfully_parsed
    Successfully Parsed
    nullableboolean

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-normalize-phone-number. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-normalize-phone-number
curl -X POST 'https://v3-api.texau.com/api/v1/texau-normalize-phone-number' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"mobile_number":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "can_be_internationally_dialed": true,
    "country_code": 1,
    "e164_format": "sample",
    "international_format": "sample",
    "is_possible": true,
    "is_valid": "rec_4f3a91",
    "national_format": "sample",
    "number_type": "sample",
    "region_code": "sample",
    "rfc3966_format": "sample",
    "successfully_parsed": true
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Normalize Phone Number (Utility)→Remove Extra Whitespace (Utility)→Identify Email Type (Utility)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → normalize phone number (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Normalize Phone Number (Utility)Texau action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit1000 / min
  • Per-day limit1,000,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More Texau actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__texau-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Normalize Phone Number (Utility) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs