# WhatsApp Business Lookup — Name, Photo & Bio for Any Number (`axery/whatsapp-business-profile-lookup`) Actor

Check whether a phone number has a registered WhatsApp Business profile, and pull its display name, description and photo if so. No login, no API key.

- **URL**: https://apify.com/axery/whatsapp-business-profile-lookup.md
- **Developed by:** [Axery](https://apify.com/axery) (community)
- **Categories:** Developer tools, Other, Integrations
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## WhatsApp Business Profile Lookup

Checks whether a phone number has a registered WhatsApp Business profile, and pulls its display name, description and photo when it does. No login, no API key.

Useful for sales lead qualification (does this prospect have a WhatsApp Business presence?), CRM enrichment, and verifying a business's WhatsApp contact before adding it to an outreach list.

### What makes this different — and what it honestly doesn't claim

WhatsApp's own `wa.me/{number}` page — the same link every "Chat on WhatsApp" button on the web points at — carries real Open Graph metadata (name, description, photo) when a number has a registered Business profile, and falls back to identical generic copy when it doesn't. This Actor reads that distinction directly.

**It does not, and does not claim to, validate whether an arbitrary personal number has WhatsApp installed.** WhatsApp doesn't expose that on this public page for anyone — no tool that isn't the WhatsApp client itself legitimately can. A "validator" that claims otherwise for personal numbers is making a claim its method can't support. This Actor is scoped to what the signal actually proves: `has_business_profile` is true only when WhatsApp itself serves a real business name for that number, and false otherwise — never a broader claim about number validity.

### Input

| Field | Type | Notes |
|---|---|---|
| `numbers` | array | Phone numbers with country code, any common formatting. |
| `proxyConfiguration` | object | Not normally needed. |

### Output

```json
{
  "input": "+1 415 523 8886",
  "phone_digits": "14155238886",
  "has_business_profile": true,
  "business_name": "Twilio",
  "business_description": "Business Account",
  "profile_image_url": "https://pps.whatsapp.net/v/...",
  "chat_url": "https://wa.me/14155238886"
}
```

A number without a registered profile still produces a row — `has_business_profile: false` with the other business fields null — rather than being silently skipped, so a full input list always maps to a full output list. Each run also writes a `RUN_COVERAGE` record to the key-value store with what was requested and what came back.

### Local development

```bash
pip install -r requirements.txt
python test_local.py "+1 415 523 8886" "19998887777" --out sample_output.json
```

`sample_output.json` is real output from a live lookup.

# Actor input Schema

## `numbers` (type: `array`):

Phone numbers with country code, in any common format (spaces, dashes and a leading + are all fine - only the digits matter). Each is looked up independently into the same dataset.

## `proxyConfiguration` (type: `object`):

Apify Proxy settings. WhatsApp's wa.me page is public, but Apify's own container IP range can still be rate-limited or blocked by services that treat cloud IPs as suspicious regardless of any WAF - defaults to Residential as a precaution.

## Actor input object example

```json
{
  "numbers": [
    "+1 415 523 8886"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per number: whether it has a registered WhatsApp Business profile, and its name/description/photo if so.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "numbers": [
        "+1 415 523 8886"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("axery/whatsapp-business-profile-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "numbers": ["+1 415 523 8886"] }

# Run the Actor and wait for it to finish
run = client.actor("axery/whatsapp-business-profile-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "numbers": [
    "+1 415 523 8886"
  ]
}' |
apify call axery/whatsapp-business-profile-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,axery/whatsapp-business-profile-lookup"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/HjeAB56rWOT0w24Yi/builds/nArJQZdTIqCbQhQsw/openapi.json