Use case

Stop fraud & fake signups

Flag disposable emails, invalid numbers and risky IPs at the door — before they ever reach your database.

A new signup or checkout

POST /v1/validate/emailPOST /v1/validate/phoneGET /v1/geoip

Risk signals before you commit

Book a demo View API docs

The flow

How the flow works

01POST /v1/validate/email
Email Validation
Flag disposable, role and undeliverable email addresses.
API details
02POST /v1/validate/phone
Phone Validation
Confirm the number is valid and return carrier and line type.
API details
03GET /v1/geoip
IP Geolocation
Add a network and country risk signal from the IP.
API details

See it

The flow in code

the flow · example

POST/v1/validate/email200 OK

{
  "valid": true,
  "deliverable": true,
  "disposable": false,
  "free": false
}

POST/v1/validate/phone200 OK

{
  "valid": true,
  "country_code": "US",
  "carrier": "Verizon",
  "line_type": "mobile"
}

GET/v1/geoip200 OK

{
  "country": "United States",
  "country_code": "US",
  "currency": "USD",
  "isp": "Google LLC"
}

Try every endpoint in the playground

One integration

Piece it together, or ship one flow

Fake signups don’t announce themselves. A disposable inbox, a VoIP number and a datacenter IP each look fine on their own — together they’re a bot draining your free tier or a fraud ring probing checkout. Screening them one vendor at a time means three integrations, three bills and blind spots in between.

Piece it together yourself

Vendors: Email, phone and fraud — 3 tools
Coverage: Gaps between providers
Setup: Weeks wiring 3 SDKs
Cost: 3 subscriptions

One Locanium flow

Vendors: 1 Locanium key
Coverage: Email + phone + IP in one call
Setup: One request, ship in a day
Cost: One usage-based bill

Why Locanium

Why teams build it on Locanium

Three checks, one flow

Email, phone and IP risk in a single integration — no separate anti-fraud vendor.

Blocked at the door

Reject disposable emails and invalid numbers before they hit your database.

Carrier-grade signals

E.164 formatting, carrier and line-type detection out of the box.

One key, one bill

Every check runs off the same Locanium key.

<40ms
Median response: 3
Checks per flow: 1
Key, no vendors

Ship it

Step-by-step guides for this flow

Stop fake signups: validate emails before they hit your database

Read guide

Format and verify international phone numbers before you send an SMS

Read guide

FAQ

Questions developers ask

How long does integration take?

One HTTP call per check — most teams ship the full flow in an afternoon, with SDKs for JavaScript, Python and Go.

Does it add latency to signup?

Sub-40 ms median per call. Run the three checks in parallel and the whole flow adds roughly 40 ms — invisible to the user.

How current is disposable-email detection?

The disposable and role-address lists are refreshed continuously from live signals, not a static file that goes stale.

Do you retain the data we send?

Requests are processed in-memory and not stored. See our DPA and subprocessors for the full data-handling detail.

Can I block, or just score?

Both. Every response is structured, so you can hard-block disposable emails and invalid numbers, or feed the risk signals into your own scoring model.