Create API key
Open the app API Center and create a server-side key. The plaintext key is shown only once.
ZelNum uses one task-based API for phone validation, carrier and HLR lookup, WhatsApp, Telegram, and account-signal workflows. Submit a product slug, poll the task, then download the result file.
https://api.zelnum.com/api/v1
X-API-Key: YOUR_API_KEYPOST /api/v1/realtime/check/{series}.POST /api/v1/detect or POST /api/v1/detect/file.The app documentation is the source of truth for product slugs, limits, response fields, and examples. The marketing site links users there instead of publishing stale product-specific endpoints.
Open the app API Center and create a server-side key. The plaintext key is shown only once.
Send a product slug, country code, and phone list to the unified detect endpoint.
Use the returned task ID to monitor pending, processing, completed, or failed status.
After completion, request the result download URL and import the CSV/TXT output into your workflow.
Use server-side API keys and keep credentials out of browsers, mobile apps, and public repositories. Replace the product slug with the one listed in the live app docs or returned by GET /api/v1/products, which needs no key.
curl -X POST "https://api.zelnum.com/api/v1/detect" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"product": "phone-status-check",
"country": "US",
"phones": ["+13125550731", "+442071838750"]
}'
For one-off checks that should return in the same call, use the realtime endpoint. It accepts one phone number or one email together with up to ten realtime product ids from the same series, and requires an Idempotency-Key so a retry never bills twice.
curl -X POST "https://api.zelnum.com/api/v1/realtime/check/phone" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Idempotency-Key: 6f1c2b7e-4d3a-4f8e-9c21-0b5a7d2e9f10" \
-H "Content-Type: application/json" \
-d '{"identifier":"+13125550731","country":"US","product_ids":[47]}'
POST /api/v1/detect/file uploads CSV or TXT files.GET /api/v1/products lists every product with its series and minimum quantity.GET /api/v1/tasks/{task_id}/result returns the download URL.GET /api/v1/balance checks account balance.GET /api/v1/tasks/{task_id} checks progress.POST /api/v1/detect submits phone arrays.The full contract is published as an OpenAPI 3.1 document at zelnum.com/openapi.yaml. It carries every path, the security schemes, the complete business error-code enum, and the rate-limit headers, so it can drive SDK generation, Postman collections, and API tooling without scraping the documentation page.
API results are verification and data quality signals. Coverage, confidence, and response fields can vary by country, product, source, and identifier quality. ZelNum does not prove identity or replace legal, consent, or compliance review.
Use authorized data only. ZelNum provides verification signals, not identity proof, legal approval, or permission to contact a person.
Use the product pages for individual lookups, upload a file for bulk checks, or submit an asynchronous job through the API.
Use a single-number lookup when you need an immediate result.
Open a lookup toolUpload CSV or TXT lists, run the selected checker, and download segmented results.
Browse productsSubmit a job, poll its status, and download structured results from the API.
Read the API guideOpen ZelNum in your preferred AI assistant to review its bulk WhatsApp, Telegram, phone validation, carrier lookup, social account, crypto exchange, CSV upload, and API workflows.
The prompt points assistants to ZelNum.com, live pricing, product pages, and API documentation.