What this API does and who it is for

Whatsapp Data provides programmatic access to publicly available WhatsApp profile data. At its core, you supply a phone number and receive back whatever that number's owner has made public on WhatsApp: their display name, push name, about/status text, profile picture URL, country code, and whether the number is registered on WhatsApp at all. For business accounts the response is richer, including a business description, categories, website links, and business hours.

The target audience is developers building identity-enrichment pipelines, CRM tools, contact verification flows, or fraud-detection systems where confirming that a phone number is a live WhatsApp account adds signal. The provider also surfaces carrier lookup, phone data-breach history, device count, and a Google Maps phone search — making this closer to a multi-purpose phone intelligence tool than a single-purpose WhatsApp checker.

One important caveat upfront: profile picture retrieval is not guaranteed for regular (non-business) accounts due to WhatsApp's ongoing anti-bot enforcement. The provider maintains a 200+ GB historical picture database and can serve cached images via /picture/{number}, but live fetching of non-business profile pictures may fail silently.

Key capabilities and endpoint walkthrough

The endpoint list runs to 65 entries in total (many are duplicates across API versions). The practically distinct operations are:

Profile lookup

  • GET /number/{number} — The primary endpoint. Returns name, phone, country code, about text, profile picture URL, isBusiness, isWAContact, and full business profile fields when applicable. The number must be passed without dashes or special characters (e.g., 59898297150).
  • GET /number/no_picture/{number} — Identical to the above but skips the profile picture fetch, which can improve reliability for non-business numbers.
  • GET /picture/{number} — Retrieves the last saved picture from the provider's cached database rather than attempting a live fetch.

Bulk and batch operations

  • POST /bulk/check/task/create and GET /bulk/check/task/list — Asynchronous task-based bulk lookup for processing many numbers without hitting per-second rate limits synchronously.
  • POST /phone-numbers/bulk-check/basic and /full — Synchronous bulk checks at basic and full detail levels.
  • POST /bulk_check — An older bulk endpoint also present in the listing.

Supplementary lookups

  • GET /carrier/{phone} — Carrier/operator lookup for a phone number.
  • GET /leakcheck/{phone} and GET /check_leaks/{number} — Data breach history for a phone number, with the leakcheck variant requiring no external API key.
  • GET /device_count/{number} — Returns the number of devices associated with a WhatsApp account.
  • GET /telegram/check — Profile information lookup on Telegram.
  • GET /gmap/{phone} — Searches Google Maps using a phone number.

Private instance endpoints

  • GET /private-instance/instances, GET /private-instance/auth/qr, GET /private-instance/profile/{number} — For users who operate their own WhatsApp session via the API, enabling authenticated profile picture retrieval that bypasses some of the public-fetch restrictions.

Pricing breakdown

The API uses a freemium model with four tiers:

Plan Price Monthly requests Overage Rate limit
BASIC $0 50 — —
PRO $35 10,000 $0.0100/req 2 req/sec
ULTRA $139 50,000 $0.0080/req 2 req/sec
MEGA $449 500,000 $0.0050/req 4 req/sec

The free BASIC tier grants 50 requests per month — enough for testing and exploring the response shape, but not for any production workload. PRO at $35/month makes sense for low-volume tools where number validation is an occasional enrichment step rather than a core loop. ULTRA and MEGA are targeted at higher-volume data pipelines; the MEGA plan's overage rate drops to half a cent per request, which is meaningful when processing large contact lists. Enterprise and custom plans are available by contacting the provider directly.

Practical use cases

  • Contact validation before outreach: Confirm that a collected phone number is an active WhatsApp account before routing a message campaign, reducing wasted sends.
  • CRM enrichment: Append display names and business profile data to contact records ingested from lead forms.
  • Fraud or identity checks: Combine the WhatsApp validity check with the carrier lookup and breach history endpoints to build a lightweight phone reputation signal.
  • Business directory verification: Confirm that a claimed business WhatsApp number actually resolves to a verified business profile with matching categories and website.

Limitations to evaluate before integrating

Several numbers from the fact sheet deserve serious consideration before committing to this API in a production system.

Success rate: The measured average success rate is 58%. For a validation or enrichment API, this means roughly four in ten calls will not return usable data. The provider attributes failures to WhatsApp's anti-bot countermeasures and documents 96% uptime, but uptime and response success are different metrics — the API can be reachable while still returning errors or empty results for individual numbers.

Latency: The average response time is 3,582 ms. This rules out synchronous use cases where the lookup sits in a user-facing request path. For background enrichment jobs or asynchronous pipelines the latency is more tolerable, and the bulk task endpoints are better suited to high-volume work regardless.

Profile picture availability: Non-business profile pictures are explicitly described as not guaranteed. If picture retrieval is a core requirement of your integration, plan around the cached /picture/{number} endpoint and test against your actual target numbers before assuming coverage.

Third-party data: This is a scraping/automation-based API, not an official WhatsApp API. Service continuity depends on the provider's ability to maintain sessions against WhatsApp's evolving bot-detection systems. The provider publishes a live API status page at https://whatsapp.checkleaked.cc/api-status which is worth bookmarking.

Getting started

The BASIC plan requires no upfront payment, so the lowest-friction path is to sign up, make a few calls to GET /number/{number} with real test numbers, and inspect the response schema before choosing a paid tier. Pass numbers without any formatting characters — digits only, including the country code prefix. For bulk workflows, the POST /bulk/check/task/create flow will be more efficient than looping over the single-number endpoint at scale, and it better respects the per-second rate limits on paid plans. For questions about enterprise volume or private instance configuration, the provider's contact is [email protected].