← Back to 888 Number Check

Phone Number Verification API

RESTful phone number verification API — validate numbers, check WhatsApp & Telegram registration, detect carriers, and verify 40+ apps programmatically. Python, Node.js, PHP, Go SDKs. 99.99% accuracy across 200+ countries.

Developer-First Phone Verification

Simple REST API with SDKs for Python, Node.js, PHP & Go. Webhook callbacks. Async batch processing. Start in 5 minutes.

Read Integration Guide

API Endpoints

POST /api/v1/verify — Single number verification
POST /api/v1/verify/bulk — Bulk verification (up to 100K per batch)
POST /api/v1/verify/async — Async verification with webhook callback
GET /api/v1/status/:job_id — Check async job status

Example Request

curl -X POST https://api.numbercheck.live/v1/verify \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "phone": "+12125551234",
    "checks": ["whatsapp", "telegram", "carrier", "format"]
  }'

# Response
{
  "phone": "+12125551234",
  "valid": true,
  "country": "US",
  "carrier": "Verizon Wireless",
  "line_type": "mobile",
  "whatsapp": true,
  "telegram": true,
  "whatsapp_business": false
}

SDKs & Languages

Pythonpip install numbercheck
Node.jsnpm i numbercheck
PHPcomposer require numbercheck
Gogo get numbercheck
RESTAny HTTP client

What the API Checks

CapabilityEndpointResponse Time
Format Validation (E.164)/verify< 100ms
Carrier Detection (HLR)/verify< 500ms
Line Type (Mobile/Landline/VoIP)/verify< 100ms
WhatsApp Registration/verify< 300ms
Telegram Registration/verify< 300ms
40+ App Detection/verify< 2s (all apps)
Bulk Verification/verify/bulk100K / 5 min
Async + Webhook/verify/asyncWebhook on completion

Why Choose This API

Multi-Source Verification

Unlike APIs that only check format, our API performs multi-path verification: HLR lookups (carrier-level), SS7 signaling (network-level), and direct app API queries (platform-level). When one path fails, automatic fallback ensures maximum accuracy. How the technology works →

Global Coverage

200+ countries with local carrier interconnects. Reliable verification across Southeast Asia, Middle East, Latin America, Africa, and all major markets. Not just US/EU — we specialize in emerging markets where other APIs fail. Country coverage guide →

Developer Experience

Clean RESTful design, consistent JSON responses, comprehensive error codes. SDKs for Python, Node.js, PHP, Go with full type hints. Webhook callbacks, async processing, rate limiting controls. Built by developers, for developers.

Use Cases

Frequently Asked Questions

What is a phone number verification API?

A phone number verification API is a RESTful web service that programmatically validates phone numbers. It checks format validity (E.164 standard), carrier status (HLR lookup), line type (mobile/landline/VoIP), and app registration status (WhatsApp, Telegram, Facebook, etc.). Developers integrate it via HTTP requests to validate numbers in real-time or batch.

What SDKs and languages are supported?

We provide official SDKs for Python, Node.js, PHP, and Go. The API is RESTful and language-agnostic — any language that can make HTTP requests (Java, Ruby, C#, Rust, etc.) can integrate directly. See the API integration guide for code examples and quickstart tutorials.

How does the bulk verification API work?

The bulk API accepts arrays of phone numbers via POST request, processes them in parallel across multiple carrier APIs, and returns structured JSON results classifying each number as active, inactive, or invalid. For large batches (10K+), use the async endpoint with webhook callbacks. Processing speed: 100K numbers in under 5 minutes.

Is there a free tier for the phone verification API?

We offer free web-based tools for individual number checks. For API access, plans start at $1 per 10,000 verifications. Contact us on Telegram (@ayongzhanshen) for developer accounts, testing credits, and enterprise pricing with custom SLAs.

How accurate is the phone verification API?

99.99% accuracy through multi-path verification: HLR (Home Location Register) lookups, SS7 signaling queries, and direct carrier API integrations. When one verification path fails, an automatic fallback verifies through an alternative channel. This ensures maximum reliability even in regions with unreliable carrier infrastructure.