Name Lookup API for Digital Identity Discovery
Turn any name into a structured identity profile. ClearCheck Data returns matched social profiles, usernames, linked email addresses, phone numbers, web presence signals, and an identity confidence score — all in one API call.
From a Name to a Full Digital Identity Profile
The Name Lookup API accepts a person's full name and searches across public signals to return matched profiles, usernames, linked contact data, and web presence indicators — ranked by confidence in a single structured JSON response.
Profile Matching
Match the submitted name against public identity records and social profiles. Each result includes a confidence rank so you can prioritize the most likely matches for review or further enrichment.
Social Graph
Discover which social networks, public platforms, and online communities the name appears in. Useful for building an identity picture from public signals without manual research.
Username Discovery
Return platform handles and usernames associated with this name across detectable public sources. Pass usernames to further lookup flows to build a more complete cross-platform identity profile.
Web Presence
Detect whether the name has a meaningful public web presence — news mentions, professional listings, or public records. A verified web presence is a strong positive identity signal.
Linked Contact Data
Returns email addresses and phone numbers found to be associated with this name. Pass them to the Email or Phone Lookup API to continue enrichment and cross-reference identity signals.
Confidence Score
Each lookup returns a confidence score from 0 to 10. Higher means more consistent signals. Use it directly in your risk rules to approve, flag, or escalate accounts.
What You Send
A person's full name is the primary input. Optionally include location context to improve match accuracy for common names.
Full Name
First and last name in standard format — e.g. John Smith. Middle names and suffixes are supported.
API Key
Sent as a Bearer token in the Authorization header. Always kept server-side — never in browser code.
Lookup ID
A reference integer you assign. Returned as-is in the response so you can match results to your own records.
What You Get Back
Every completed lookup returns a structured JSON object. Here is what each field means and how to use it.
Submit, Receive, Poll, Parse
The name lookup runs through an async enrichment pipeline. Submit your request, hold the job ID, and poll when ready. Your backend keeps processing without waiting.
Submit the Name
POST the full name with your Bearer API key. The same endpoint accepts phone, email, name, and image lookups.
Receive Job ID
The API responds immediately with a numeric job ID and status "progress". No waiting required at this step.
Poll for Completion
Query the monitor endpoint using the job ID. When status changes to "completed", all matched profiles and signals are ready.
Parse & Route
Receive normalized JSON. Route high-confidence matches to review queues or pass linked emails and phones to further lookup APIs.
How to Make a Name Lookup Call
Send one POST request with the full name and your API key. Get a job ID back straight away — no waiting. Poll once to pick up the full result when it's ready.
The same endpoint handles all lookup types. Change lookup_type to switch between name, phone, email, or image — everything else stays the same.
Docs are currently on our existing portal and will move to the ClearCheck Data portal soon.
// 1. Submit lookup POST /api/developer/combined_name Authorization: Bearer YOUR_API_KEY Content-Type: application/json { "lookup_type": "name", "value": "John Smith", "lookup_id": 44 } // 2. Initial response { "id": 8821045, "status": "progress" } // 3. Poll for result GET /api/request-monitor/api-usage/8821045 // 4. Completed response { "status": "completed", "identity_score": 7.2, "signals": { "profiles": ["example_profile"], "usernames": ["example_handle"], "linked_emails": ["j***@example.com"], "confidence_rank": 8 } }
Who Uses Name Lookup and Why
Name enrichment is used wherever a submitted name needs to be verified, profiled, or connected to additional identity signals for risk, compliance, or investigation workflows.
OSINT & Investigations
Build structured identity profiles starting from just a name. Linked social accounts, usernames, emails, and phones help investigators corroborate identity and trace connections.
KYC & Onboarding
Cross-reference submitted names against publicly available identity signals during onboarding. High-confidence profile matches and linked contact data strengthen identity verification flows.
Fraud Prevention
Flag names with no detectable public presence, inconsistent contact links, or low confidence scores. These are signals that warrant additional verification before approving an account.
Marketing & CRM
Enrich contact records with linked emails, phones, and social profiles. Keep CRM data current and improve contact reachability without manual research for each record.
Risk Orchestration
Feed name confidence scores and profile data directly into your rules engine. Structured JSON integrates with any decision system without additional transformation.
E-commerce Verification
Verify submitted buyer or seller names by checking for a consistent digital identity. Names with no web presence or inconsistent linked data are worth additional review before a transaction.