Use Case · Phone Enrichment

Phone Lookup API for Identity & Risk Signals

Turn any phone number into a structured identity profile. ClearCheck Data returns carrier data, line type, risk score, linked email addresses, social profiles, and digital signals — all in one API call.

  • Carrier, line type, country, and active status
  • Risk score and spam / fraud indicators
  • Linked email addresses, social profiles, and messaging apps
  • Identity confidence score (0–10) and linked digital signals
PHONE LOOKUP · Live
Input+1 (415) 555-2671
CarrierVerizon WirelessVerified
Line TypeMobile · ActiveConfirmed
Risk Score0.12 / LowSafe
Profiles4 foundEnriched
Score7.4 / 10Strong
What It Does

From a Phone Number to a Full Identity Signal Set

The Phone Lookup API accepts any E.164-formatted phone number and returns a normalized set of enrichment signals in a single structured JSON response.

📡

Carrier & Network Data

Identify the carrier, network type (mobile, landline, VoIP, prepaid), and home country. Useful for routing decisions, fraud detection, and onboarding risk scoring.

Linked Email Discovery

Returns email addresses found to be associated with this phone number. Use them to cross-reference records or continue enrichment with the Email Lookup API.

🚨

Fraud Risk Signals

Receive a composite risk score and spam flag based on fraud pattern signals, abuse history, and network-level indicators.

🔗

Linked Identity Signals

Discover which messaging platforms, social applications, or digital services are associated with this phone number.

📍

Location Signals

Detect the registered country, region, and roaming status. Flag numbers in high-risk regions or mismatched against user-submitted location data.

Confidence Score

Each lookup returns a score from 0 to 10. Higher means more consistent signals. Use it directly in your risk rules to approve, flag, or escalate accounts.

Output Signals

What You Get Back

FieldDescription
carrier

The mobile operator that owns this number — useful for routing decisions and detecting virtual operators.

line_type

Mobile, landline, VoIP, or prepaid. VoIP and prepaid lines carry higher fraud risk by default.

country

Where the number is registered. A mismatch with the user's stated location is a red flag.

risk_score

A 0–1 number. Above 0.6 is worth a closer look. You define your own threshold in your rules engine.

spam_flag

True if the number appears in known spam or abuse databases — treat this as a hard block signal.

linked_emails

Email addresses associated with this number. Pass them to the Email Lookup API for deeper enrichment.

linked_profiles

Social network and public profile handles connected to this number, where detectable.

identity_score

0–10 composite score. Score of 7+ means strong, consistent signals. Use it directly in your risk rules.

API Workflow

Submit, Receive, Poll, Parse

The phone lookup runs through an async enrichment pipeline. Submit your request, hold the job ID, and poll when ready.

1

Submit Phone Number

POST the phone number with your Bearer API key. The endpoint accepts E.164-formatted numbers globally.

2

Receive Job ID

The API responds immediately with a numeric job ID and status "progress". No waiting required at this step.

3

Poll for Completion

Query the monitor endpoint using the job ID. When status changes to "completed", the full signal set is ready.

4

Parse & Route

Receive normalized JSON. Route risk scores to your rules engine, store carrier data in your CRM, or trigger review workflows.

POST/api/developer/combined_phoneJSON
// 1. Submit lookup
POST /api/developer/combined_phone
Authorization: Bearer YOUR_API_KEY
{
  "lookup_type": "phone",
  "value": "+14155552671",
  "lookup_id": 42
}
// 2. Initial response
{ "id": 8821043, "status": "progress" }
// 3. Completed response
{
  "status": "completed",
  "data": {
    "carrier": "Example Carrier",
    "line_type": "mobile",
    "risk_score": 0.12,
    "confidence": 0.94
  }
}

Docs are currently on our existing portal and will move to the ClearCheck Data portal soon.

Use Cases

Who Uses Phone Lookup and Why

🛡

Fraud Prevention

Flag high-risk numbers at account registration or transaction time. Risk scores, spam flags, and VoIP/prepaid detection help intercept fake accounts.

Learn more →

KYC & Onboarding

Enrich submitted phone numbers during identity verification flows. Carrier data, line type, and active status supplement other identity signals.

Learn more →

Risk Orchestration

Feed phone signals directly into your rules engine or risk scoring platform. Structured JSON integrates with any decision system.

Learn more →
🛒

E-commerce & Marketplaces

Verify buyer and seller contact data before transactions. Detect disposable numbers, prepaid burners, and VoIP lines.

Learn more →
🔍

OSINT & Investigations

Enrich phone numbers submitted during investigations. Carrier data, linked app signals, and geographic information help build a structured profile.

Learn more →
📊

Marketing & CRM Hygiene

Validate phone numbers in contact lists before outreach. Filter disconnected, inactive, or invalid numbers.

Learn more →

Frequently Asked Questions

The API accepts E.164-formatted phone numbers (e.g., +14155552671). This format covers US, EU, and global numbers.
Most phone lookups complete in under 0.5 seconds. The async pipeline allows your system to continue processing while enrichment runs.
The risk score (0–1) aggregates multiple signals including fraud history, number type (VoIP/prepaid), spam database matches, and behavioral patterns. Define your own threshold in your rules engine.
Yes. The line_type field returns mobile, landline, VoIP, or prepaid. VoIP and prepaid numbers carry higher default risk scores.
ClearCheck Data processes lookups according to its data handling policy. Phone numbers are used to retrieve enrichment signals and are subject to the Data Processing Addendum.
Yes. The API supports global phone numbers in E.164 format, with varying signal depth by region.

Ready to Start Enriching Data?

Get API access and start enriching phone numbers, emails, names, and digital signals in minutes.