Caller identity
Reveal available caller records and match confidence from lookup data.
Search a mobile number, review available caller records, check telecom circle signals, and integrate the same lookup flow into your own product through the existing API.
WhoCalled.in is built like an advanced Truecaller-style lookup experience: search a number, review available identity signals, detect suspicious patterns, and route verified data into your workflows.
Reveal available caller records and match confidence from lookup data.
Spot suspicious numbers and repeated unwanted call patterns faster.
Send lookup intelligence into apps, CRMs, and fraud review dashboards.
Instantly discover registered names behind unknown numbers using database shard analysis.
Identify telemarketing, robotic, and automated fraud numbers using real-time call risk analysis.
Integrate caller ID and location directory services inside your applications via high-speed JSON pipelines.
Scan mobile networks, operator circles, and activation timestamps across global nodes.
Cross-border database engines compile multi-country registers into unified search tables.
Lookups are secure and private. Easily manage your record settings with direct opt-out tools.
A professional number lookup product needs more than a pretty input. It needs clear data handling, API reliability, anti-abuse controls, conversion paths, documentation, and search visibility.
Clear policies, data request pages, opt-out language, and responsible-use copy are included so the product feels safer and more credible.
The homepage now explains why visitors should search, when they should upgrade, and how developers can use the API.
Focused supporting pages target reverse lookup, caller ID API, spam checking, and telecom circle lookup keywords.



The website search still posts to /api/search. The frontend upgrades do not change your backend route, request method, or JSON payload.
Nginx deploy notes include an API proxy area where you can add WAF, limits, and abuse protection.
CTA, consent, contact, pricing, and lookup intent events can be pushed to analytics without changing the lookup backend.
Developer copy and code examples reduce friction for SaaS, CRM, fraud, and support integrations.
POST /api/search
Content-Type: application/json
{
"query": "9999999999",
"limit": 50
}
Signals shown when available:
- name
- mobile
- alt phone
- telecom circle
- country
- match score
Type any mobile number, name, or corporate record into our search field.
Our backend queries indexed document shards across operator-linked telecom databases.
Review caller name registry, location circle, networks, and spam warnings in real time.
Ideal for testing basic reverse lookups.
Ideal for temporary or short-term search needs.
Designed for daily phone lookup and caller checks.
Best value for long term caller identity lookup.
These sections are placeholders for your real numbers, reviews, partners, and case studies. They are structured so you can replace them with live proof before launch.
Used lookup signals to triage suspicious onboarding records before manual review.
Enriched inbound caller records with available identity and region context.
Flagged repeat suspicious numbers and improved callback decision quality.
These pages give search engines focused URLs and give backlink outreach something useful to reference.
Search intent page for users asking who called them from an unknown number.
Developer-focused page for API buyers and integration partners.
Informational page for fraud, spam call, and unknown caller risk searches.
Educational resource for earning links from support and safety content.
Downloadable-style template page for suspicious call documentation.
Operational trust page for uptime, latency, and incident reporting.
Capture serious buyers without disturbing the public lookup backend. Connect this form to your CRM, email automation, or ticketing system before production launch.