Single Number Checker
Best for confirming one lead, reviewing a customer record, or testing how WhatsApp validation works before integrating the API.
Try the Free Checker WhatsApp number validator for developers
WhatsApp Number Validator API — Bulk Validate 1,000 Numbers per Batch
ProWebLook's WhatsApp number validator API processes up to 1,000 phone numbers per batch. Submit once, receive a batch_id instantly, then poll for WhatsApp registration status, Business account detection, carrier, country, and per-number results.
1,000Numbers per batch
202Accepted response
1:1WA credit per number
batch-response.json
processing
{
"batch_id": "550e8400-e29b...",
"total_numbers": 1000,
"status": "processing",
"next": "poll_results"
}
872completed
116pending
12failed
Async batch workflow
Async WhatsApp Number Validator for High-Volume Contact Lists
ProWebLook's WhatsApp number validator API separates submission from results so CRM cleanup jobs, lead enrichment pipelines, and phone number validation workflows run without blocking your application.
1
Submit the batch
POST a JSON array of phone numbers with your API key. Duplicates are removed automatically and the maximum request size is 1,000 numbers.
2
Queue processing
The API returns a unique batch ID immediately. Each number is validated asynchronously and starts in processing or pending state.
3
Poll for results
Call the poll endpoint with the same API key until the top-level status becomes completed, then export or sync the finished results.
What you get
Bulk results that are ready for your CRM
Use structured result fields to segment WhatsApp-ready numbers, detect business accounts, retry temporary provider failures, and keep malformed records out of your campaigns.
WhatsApp status
Identify numbers that are registered on WhatsApp and separate contacts that cannot receive WhatsApp messages.
Business detection
Spot WhatsApp Business accounts with the businessnumber field for lead scoring and account enrichment.
Carrier and country
Use formatted numbers, carrier, and country values to normalize records before import or outreach.
Retry-friendly states
Completed, failed, and pending counts make it easy to retry only the rows that need another attempt.
API examples
Submit once, poll until completed
The submit endpoint checks your WA credit balance upfront. If you submit 500 numbers, you need at least 500 WA credits available before the batch is accepted.
0Unique numbers
0WA credits needed
5-10sSuggested polling
Paste a list to estimate your batch size. Maximum: 1,000 numbers per request.
curl -X POST "https://lookup.proweblook.com/api/v1/wavalidation/batch" \
-H "Content-Type: application/json" \
-d '{
"api_key": "YOUR_API_KEY",
"phone_numbers": [
"+14155552671",
"+919876543210",
"+441234567890",
"+33123456789"
]
}'
const response = await fetch(
'https://lookup.proweblook.com/api/v1/wavalidation/batch',
{
method: 'POST',
headers: {'Content-Type': 'application/json'},
body: JSON.stringify({
api_key: 'YOUR_API_KEY',
phone_numbers: ['+14155552671', '+919876543210']
})
}
);
const batch = await response.json();
console.log(batch.batch_id);
import requests
url = "https://lookup.proweblook.com/api/v1/wavalidation/batch"
payload = {
"api_key": "YOUR_API_KEY",
"phone_numbers": ["+14155552671", "+919876543210"]
}
response = requests.post(url, json=payload)
batch = response.json()
print("Batch ID:", batch.get("batch_id"))
curl "https://lookup.proweblook.com/api/v1/wavalidation/batch/550e8400-e29b-41d4-a716-446655440000?api_key=YOUR_API_KEY" // Poll every 5-10 seconds for small batches. // Use 30-60 seconds for batches near 1,000 numbers.
| Endpoint | Method | Purpose | Key fields |
|---|---|---|---|
/api/v1/wavalidation/batch |
POST | Submit up to 1,000 phone numbers for asynchronous validation. | api_key, phone_numbers, batch_id, total_numbers, status |
/api/v1/wavalidation/batch/{batch_id} |
GET | Poll status and retrieve completed, failed, pending, and per-number results. | numberstatus, businessnumber, formatted_number, carrier, country |
Use cases
Where bulk WhatsApp validation helps
Clean the list before sending, routing, uploading, or enriching contacts. That means fewer wasted credits in downstream tools and cleaner CRM data.
CRM data cleaning
Validate old lead lists and remove contacts that are not reachable on WhatsApp before assigning them to sales teams.
Campaign preparation
Segment WhatsApp-ready audiences before campaign upload so your outreach list starts with better deliverability.
Fraud and signup checks
Check batches of submitted phone numbers to spot low-quality signups or contacts that need additional review.
Data enrichment pipelines
Add WhatsApp presence, business account, carrier, and country signals to your existing data warehouse workflows.
Use validation responsibly. Validation confirms availability, not consent to contact. Make sure every campaign follows the recipient's permission and the messaging rules that apply to your business.
Choose the right workflow
Bulk vs. Single Check: Which Do You Need?
Start with the free checker for an occasional lookup. Move to the batch API when the list belongs in an automated or repeatable workflow.
Asynchronous Batch API
Best for CRM exports, imports, consented campaign data, and enrichment pipelines. A 10,000-number list requires 10 batches at the 1,000-number limit, with each batch polled until completion.
View the API Examples
Data handling
What Happens to the Numbers You Submit?
The batch workflow keeps the operational records needed to process jobs, show account history, and make finished reports available.
Operational records
The platform records batch and per-number data for processing status, account reports, and CSV exports.
No message or OTP
Validation checks account availability without sending a WhatsApp message or OTP to the submitted number.
Retention details
Review the Privacy Policy for current retention and service-provider information before sending personal data.
Quick reference
WhatsApp bulk validator — API specifications
ProWebLook's WhatsApp number validator is a REST API that accepts a JSON array of up to 1,000 phone numbers and validates each asynchronously. Built for developers and data teams running phone number validation at scale.
- No message or OTP sent to target numbers
- Returns WhatsApp status, business flag, carrier and country per number
- 1 WA credit per number — balance checked at submission
- E.164 formatting is recommended for consistent international processing
| Submit endpoint | POST /api/v1/wavalidation/batch |
| Poll endpoint | GET /api/v1/wavalidation/batch/{batch_id} |
| Max batch size | 1,000 phone numbers per request |
| Credit cost | 1 WA credit per number, deducted upfront |
| Phone format | E.164 recommended (+14155552671) |
| Duplicate handling | Automatic removal before processing |
| Submit response | HTTP 202 Accepted + batch_id immediately |
| Result fields | phone_number, status, wa_status, numberstatus, businessnumber, formatted_number, carrier, country |
| Recommended polling | 5–10s (≤100 numbers) · 30–60s (≤1,000 numbers) |
| Auth method | api_key in the POST body when submitting; api_key in the GET query when polling |
FAQ
Frequently Asked Questions
Practical answers based on the current batch submit and polling workflow.
Submit from 1 to 1,000 phone numbers per request. Duplicate values are removed before processing, and the submit response reports the number of unique records queued.
The submit endpoint returns a batch_id. Call the poll endpoint with that batch_id and the same API key until the top-level status becomes completed.
The API checks and deducts 1 WA credit per number at submission. Duplicate values are removed before processing, so use the unique-number count when estimating the balance you need.
Poll every 5–10 seconds for batches under 100 numbers and every 30–60 seconds for batches near 1,000. Avoid polling more frequently than every 2 seconds.
A batch must contain at least one phone number and can contain up to 1,000. For a one-off lookup, the free single-number checker is usually the simpler option.
The response shows completed, failed, and pending counts together with the per-number results currently available. Continue polling at the recommended interval until the top-level status is completed.
Failed rows are counted separately from completed and pending rows. Review their result status before deciding whether to correct and resubmit them. Do not assume that a failed row receives an automatic credit refund.
Use the single checker for one-off lookups and this batch API for CRM lists, imports, consented outreach data, and other high-volume workflows.
Yes. A completed per-number result includes businessnumber, which is true when the provider identifies a WhatsApp Business account.
The platform records batch and per-number data to provide processing status, account reports, and CSV exports. Validation does not send a message or OTP to the submitted numbers. Review the privacy policy for retention and service-provider details.
Send requests over HTTPS and keep the API key in server-side environment variables rather than public browser code. You can regenerate the key from your account profile if it is exposed.
Start Validating WhatsApp Numbers in Bulk
Create an account, get your API key, and submit your first asynchronous batch when you are ready to move beyond one-off checks.
Free Credits Included
Get FREE Credits to Start Today
Discover an extensive array of API calls across all ProWebLook APIs. No credit card required — start building in minutes.