Catalog / WhatsApp Account Existence Capability

WhatsApp Account Existence Capability API

web.whatsapp.com

Validates one international phone number and checks the public WhatsApp Web surface over live HTTP. WhatsApp does not expose an authorized unauthenticated account-existence endpoint here, so valid requests report unsupported rather than guessing registration.

  • Social & video
  • whatsapp
  • phone-number
  • account-existence
  • privacy
1 endpointDocs updated

Endpoint health

Loading verification…

Connect your agent

Connect through MCP so your agent can find this API, read its docs, and call its endpoints.

Setup guide

Add the server from your terminal.

Claude Code · terminal
claude mcp add --transport http agent-data https://agent-data.motie.dev/mcp

In Claude Code, run /mcp, select agent-data, then Authenticate. Sign in to your agent-data account in the browser.

Then ask your agent to use the WhatsApp Account Existence Capability API for your task.

Call it over HTTP

Get an API key

Sign up free, generate an API key, and set it as AGENT_DATA_API_KEY in your environment. Your first 100 calls each month are free.

Accepts exactly one E.164 phone number. The route never submits that number to WhatsApp because the public web surface has no supported unauthenticated lookup endpoint. A valid request returns `unsupported`; a live transport failure returns `unknown` and is never interpreted as not registered. No login, QR pairing, CAPTCHA bypass, profile lookup, or bulk enumeration is performed.

One international phone number. Separators such as spaces, hyphens, and parentheses are normalized.

View call pricing
cURL · Whatsapp account existence
curl --request GET --get 'https://3kpkg0jfvk.execute-api.us-east-2.amazonaws.com/prod/81a0d56d-bbf4-4a17-9791-0f38fdea6fa9/v1/whatsapp/account-existence' \
  --header "Authorization: Bearer $AGENT_DATA_API_KEY" \
  --data-urlencode 'phone_number=+989121234567'

Endpoints

Inputs and response fields for every endpoint in this API.

GETWhatsapp account existence/v1/whatsapp/account-existence

Accepts exactly one E.164 phone number. The route never submits that number to WhatsApp because the public web surface has no supported unauthenticated lookup endpoint. A valid request returns `unsupported`; a live transport failure returns `unknown` and is never interpreted as not registered. No login, QR pairing, CAPTCHA bypass, profile lookup, or bulk enumeration is performed.

Input

phone_numberRequiredQuery · string

One international phone number. Separators such as spaces, hyphens, and parentheses are normalized.

Example: +989121234567

Response

reasonstring
status"registered" | "not_registered" | "unknown" | "unsupported"
platformstring
checked_atstring (date-time)
phone_numberstring
evidence_sourcestring

Don’t see the endpoint you need?

Ask agent-data to add an endpoint or return more fields. Extensions are free and keep existing endpoints working.