Phone numbers are converted to E.164 format, country code is detected and optionally written back directly to Zoho CRM. Supports single and batch requests.
POST /v1/format-phone · 3 credits/requestContact forms, CSV imports and legacy CRM exports rarely agree on a single phone number format — spaces, parentheses, leading zeros and missing country codes all show up in the same list. The Phone Format API takes any of that and returns a single, dial-ready E.164 string, so the rest of your stack (dialers, SMS providers, CRM validation rules) can rely on one consistent shape.
Run a one-off pass over an existing Zoho, HubSpot or Salesforce export to standardize every phone field before a migration or a dedup pass.
Validate and normalize the phone number the moment a lead submits a form, instead of discovering malformed numbers weeks later in a call-center queue.
Point the integration at a Zoho CRM module and let normalized numbers be written back automatically — no manual re-entry, no separate sync job.
Two records that look different ("089 123456" vs "+49 89 123456") but are the same number in E.164 — normalize first, then dedup exactly.
curl -X POST https://api.toolbox-api.net/v1/format-phone \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone": "089/12345678", "country": "DE"}'{
"input": "089/12345678",
"e164": "+4989123456789",
"country": "DE",
"valid": true
}Send a phone number as free text, optionally with a two-letter country hint. The API parses it, infers the country when not given, and returns the canonical E.164 representation plus a validity flag — invalid or unparseable input is reported rather than guessed at.
One API key gets you this and four other APIs, sharing one quota.