WhatsApp Number Lookup — Profile, Leaks, Telegram, Bulk

Verify any WhatsApp number worldwide and get back far more than a yes/no answer. This actor returns the real profile picture (even for normal, non-business users), the about / status text, Telegram presence and profile, carrier data, Google and TrueCaller intel, and — uniquely — matches against a curated phone-number breach database (Facebook leak, Dehashed, LeakCheck Pro, HIBP).

Supports bulk input up to 100,000 numbers per run. Pay-per-event pricing: you are only charged for successful, fresh lookups.

Why this actor

Generic WhatsApp lookup actors on the store answer one question: does this number exist on WhatsApp? They typically return a profile picture only when the number is registered as a WhatsApp Business account, offer no cross-platform intelligence, and have no access to leaked phone-number records.

This actor closes those gaps:

• Profile pictures for normal users — not just businesses. If the user has a public avatar, you get the URL.
• About / status text — the short bio users set on their profile.
• Telegram cross-check — same phone, Telegram profile if it exists: username, display name, last-seen, Premium flag, verified flag, photo URL.
• Dedicated phone-number breach database — match the number against Facebook's 533M leak, Adecco, and other dumps indexed by Dehashed, LeakCheck Pro, and HIBP.
• Permanent cache — repeat queries served from our database at a fraction of the price.
• Database-only mode — query the archive without ever hitting WhatsApp.
• Bulk throughput — up to 50 concurrent workers per run.

Pricing — Pay per event

You only pay for successful results. Numbers that are not on WhatsApp, upstream timeouts, rate-limit errors, and validation failures are always free.

Event	When it fires	Price
Live WhatsApp lookup — number found	Fresh upstream check, number exists, result not served from cache	$0.0015
Cached WhatsApp lookup — number found	Served from our permanent cache, no live upstream call	$0.0002
Database-only search hit	Record found in archived / leak database, no live lookup	$0.0002
Profile picture addon	Non-default profile picture URL returned	+$0.0005
Leak / breach data addon	One or more breach records returned	+$0.002

Typical costs:

• 1,000 fresh successful lookups → $1.50
• 1,000 cached lookups → $0.20
• 50,000 fresh successful lookups → $75
• 50,000 numbers with profile pic + leak check, cache-first, 70% cache hit rate → ~$80

Input

Field	Type	Default	Description
numbers	array	—	Phone numbers in international format, with or without +. Auto-normalized (digits only).
preferCache	boolean	true	Try the permanent cache first; fall through to a live lookup only on miss.
onlyCache	boolean	false	Never make live WhatsApp calls. Pairs with the cheapest pricing tiers.
includeProfilePic	boolean	true	Include the profile picture URL when available.
includeAbout	boolean	true	Include the about / status text.
includeTelegram	boolean	false	Cross-check the same number on Telegram and return the full profile if present.
includeLookup	boolean	false	TrueCaller-style name and spam lookup.
includeGoogle	boolean	false	Cached Google search intel for the number.
includeLeaks	boolean	false	Query phone-number breach databases (FB leak, Dehashed, LeakCheck Pro, HIBP).
includeCarrier	boolean	false	Mobile carrier + country lookup.
concurrency	integer	5	Parallel workers (1 – 50).
timeoutMs	integer	30000	Per-lookup timeout in milliseconds.

Example input

{
    "numbers": ["+14155552671", "+5491112345678"],
    "preferCache": true,
    "includeProfilePic": true,
    "includeTelegram": true,
    "includeLeaks": true,
    "concurrency": 10
}

Output

Each number produces one row in the default dataset. Fields that were not requested are omitted from the output.

{
    "number": "59898297150",
    "exists": true,
    "isBusiness": false,
    "urlImage": "https://whatsapp-db.checkleaked.com/59898297150.jpg",
    "about": "Available",
    "telegram": {
        "id": 714847253,
        "username": "DeadAir94",
        "first_name": "Edu",
        "last_name": "Air",
        "premium": true,
        "user_was_online": "2026-04-17 17:20:35 UTC",
        "photoUrl": "https://.../714847253_photo.jpeg"
    },
    "leakedData": {
        "entries": [
            {
                "entry": {
                    "name": "Eduardo Airaudo",
                    "phone": "98297150",
                    "database_name": "Facebook",
                    "company": "Taquigrafia",
                    "source": { "Name": "Facebook", "BreachDate": "2019-08-01" }
                }
            }
        ],
        "results": 3
    },
    "fbLeak": {
        "data": {
            "firstName": "Eduardo",
            "lastName": "Airaudo",
            "fbId": "1217097936",
            "regionCode": "UY"
        }
    },
    "source": "fresh",
    "fetchedAt": "2026-04-23T13:26:35.807Z"
}

The source field is one of:

• fresh — live WhatsApp lookup (charged at the fresh rate)
• cache — served from our cache (charged at the cached rate)
• database — archived / leak record only (charged at the database rate)
• not-found — number not on WhatsApp (free)
• error — upstream issue, timeout, or invalid input (free)

A SUMMARY object is also written to the key-value store with per-source counts once the run finishes.

Use cases

• KYC and fraud prevention — verify that a phone number is a real, active WhatsApp user, not a burner.
• OSINT and investigations — pivot from a phone number to a real name, Facebook ID, Telegram username, and breach history.
• Lead enrichment — add first name, last name, profile picture, and region code to a contact list.
• Skip tracing — find additional channels (Telegram, leaked emails) tied to the same number.
• Security research — check whether a user's phone has appeared in a known breach before onboarding them.
• Recovery and reunification — locate a person across platforms starting from a single phone number.

Performance

• Median fresh lookup: ~1.5 seconds
• Cached lookup: <200 ms
• Sustained throughput at concurrency=20: ~800 numbers / minute
• Bulk cap per run: 100,000 numbers

FAQ

Am I charged when a number is not on WhatsApp? No. Only successful lookups of numbers that exist on WhatsApp are billed. Not-found and errors are always free.

Am I charged twice if I enable both profile pic and leaks? Addons stack on top of the base lookup charge. A cached lookup with pic + leaks costs $0.0002 + $0.0005 + $0.002 = $0.0027 total.

How long is the cache kept? Cached entries are permanent until overwritten by a later fresh lookup for the same number. Set preferCache: false if you need a guaranteed-live read.

What about rate limits? The upstream service handles its own rate limiting. If you exceed it, results come back with source: "error" and are not billed. Lower the concurrency value for smoother runs.

Does this actor phone home or store my numbers? Numbers are normalized, sent to the lookup backend, and the responses are written to your Apify dataset. No separate logging or retention on the actor side.

Can I run this on Apify proxy? All HTTPS calls go to a single upstream endpoint; using Apify proxy for outbound here adds latency without benefit.

Output schema

Datasets can be exported to JSON, JSONL, CSV, XML, Excel, and HTML directly from the Apify console or via API. Use the SUMMARY key-value store entry for per-run aggregates.

Feedback and issues

Open an issue on the actor's Issues tab in the Apify console, or email the maintainer listed on the store page. Feature requests welcome — especially around additional data sources and cross-platform checks.

Legal

Use this actor only for purposes permitted by your local law and the platforms whose data is returned (WhatsApp, Telegram, Facebook). You are responsible for obtaining a lawful basis before enriching, storing, or acting on the returned information — including GDPR, CCPA, LGPD, and other jurisdiction-specific rules. The operator provides lookup infrastructure only and does not warrant any specific use case.