Docs

API + Batch reference, operational notes, and examples.

Overview

e164.it exposes a minimal HTTP API to normalize phone inputs and produce VoIP / CRM-friendly outputs. You can use the web UI (Single / Batch) or call the endpoints directly.

API reference
Operational notes
  • Security — headers, rate limiting, logging hygiene
  • FAQ — common pitfalls & examples
Quick start
Single (JSON)
curl -s \
  -H "content-type: application/json" \
  -d '{"input":"0039 333 123 4567","default_region":"IT","options":{"format":["e164","rfc3966"],"classify":true,"mask":{"mode":"last4"},"hash":{"enabled":true}}}' \
  https://e164.it/v1/parse
Batch (CSV upload)
curl -s \
  -F "file=@sample.csv" \
  -F "phone_column=phone" \
  -F "default_region=IT" \
  -F "has_header=true" \
  -F "delimiter=auto" \
  -F "mask_mode=none" \
  -F "hash_enabled=false" \
  https://e164.it/v1/batch/parse \
  -o result.csv

Tip: you can also grab fixtures from Samples.

Authentication & rate limits

If this instance requires an API key, send it via x-api-key (authentication is configured server-side). The web UI stores it in sessionStorage for the current tab session (cleared when you close the tab).

The hosted https://e164.it instance may require an API key for Batch requests.

Getting an API key

Hosted service: API keys are issued by the operator. To request a key, open a GitHub issue (new issue) or contact the maintainer via LinkedIn.

Self-hosted: deploy your own instance and manage keys via the admin endpoints.

When rate limiting is enabled, responses may include: x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset.