Skip to content
zelnum.com
Phone validation API · Batch jobs · CSV in/out

Bulk Phone Validation API: Batch CSV Jobs

Validate large phone lists via API | submit batch jobs, enrich with carrier and line-type data, export clean segments for campaigns and CRM cleanup.

Batch capacity
2M rows / task
Input
CSV / API
Coverage
Global
POST /api/v1/detect
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": ["+14155550198", "+442071838750"]
  }'
Response preview
validtrue
line_typemobile
carrierdetected

Example shortened for readability. A real bulk task must meet the product minimum — 2,000 rows for phone-status-check — or the API rejects it as too_few_numbers (per the API docs, checked 2026-11-03).

Capabilities

API Capabilities

Use one API to validate phone quality, enrich records, and segment low-quality numbers before CRM or campaign workflows.

Validity check (real & active)

Determine whether a phone number appears valid, assigned, and currently in service.

Carrier & line type

Identify carrier and classify mobile, landline, VoIP, toll-free, and other line types.

Risk scoring

Flag unusual or low-confidence phone signals before outreach, CRM import, or manual review.

Country/region detection

Resolve country, region, and normalized international phone format for storage and routing.

3-minute integration

API request and response example

Batch job and CSV API workflow: create a key, normalize numbers with E.164 Phone Number Format, review mixed-country input with Validate International Phone Numbers, clean messy uploads with Data Scrubber, then submit a batch job and segment clean, risky, and invalid numbers from the JSON response.

1

Get your API key

Create a key in the ZelNum app API Center and keep it on your server.

2

Submit your first batch

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": ["+14155550198", "+442071838750"]
  }'
3

Sample batch response

Response for 5,000 accepted rows. The request above is abbreviated; a bulk job requires at least 2,000 rows.

{
  "mode": "async",
  "task_id": "xKj9aP3qLm7v",
  "message": "Task queued.",
  "summary": {
    "total": 5000,
    "cost_deducted": 3
  }
}
Reference

Endpoints Overview

Use the unified ZelNum API: submit a product slug with phone numbers, upload a file, then poll the task and download results.

POST

POST /api/v1/detect

Submit phone arrays with a product slug for async background processing.

POST

POST /api/v1/detect/file

Upload CSV or TXT files for larger list-cleaning workflows.

GET

GET /api/v1/tasks/{task_id}

Poll progress, then request the result download URL when the task is complete.

Integration stack

SDKs & Integrations

Ship validation in your existing backend stack with simple request patterns and predictable JSON responses.

Python
Node
Ruby
PHP
.NET

Pricing by product and workflow

The pricing catalog lists the price and minimum order for each product. Bulk checks are charged per 10,000 rows; single lookups have a separate per-check rate. Web uploads and bulk API tasks use the bulk workflow.

For example, HLR Lookup runs at $4 USD per 10,000 rows with a minimum batch of 2,000 — one example from the catalog. Every product has its own rate and minimum, listed on the pricing page.

View all products and prices
Developer workflows

Use Cases for List and Data Teams

Add validation wherever phone quality affects deliverability, segmentation, or data hygiene.

Bulk list cleaning workflow

Validate imported CRM lists and marketing audiences before sending SMS or WhatsApp campaigns.

Pre-campaign list enrichment

Add carrier, line type, country, and quality signals before you split, suppress, or export campaign lists.

CRM data hygiene jobs

Refresh stale phone fields, remove invalid records, and keep sales or RevOps lists easier to segment.

Comparison

Compare with Twilio Lookup / Numverify API

Compare validation scope, bulk support, pricing, and developer workflow fit before choosing an API.

Feature zelnum.com Twilio Lookup Numverify API
Bulk CSV endpoint Built in Custom workflow Limited
Single-number spot check Available Available Basic lookup
Risk scoring Included Depends on setup Not primary
Entry price See pricing catalog Usage-based Plan-based
FAQ

FAQ

Short answers for developers evaluating the zelnum.com Phone Validation API.

What's your API rate limit?
Rate limits depend on plan and volume tier. Higher-volume plans include higher throughput and optional dedicated limits.
Do you support webhook notifications?
No webhook delivery is defined in the current API contract (checked 2026-10-28). Poll the job status endpoint from your backend instead.
Do you support larger jobs?
Higher-volume plans can include priority processing, dedicated support, and custom operational requirements.
What about data privacy?
The API is designed for server-side validation, controlled access, and privacy-aware handling of phone data.
Is this a phone validator API and bulk phone validation API?
Yes. The API supports single and batch checks for phone validation. Send one number for a spot check, or submit arrays of numbers for list cleaning and high-volume jobs.
Do you offer a phone number verification API with line type and carrier fields?
Yes. The phone number verification API returns line type (mobile, landline, VoIP), carrier name, and country code per number. Suitable for list cleaning, CRM enrichment, and campaign prep.
Start validating phone lists today

Clean phone lists before campaigns and CRM import.

支柱页

Phone Validation API

This section covers the long-tail intent "Phone Validation API" inside the parent page instead of creating a duplicate URL. It connects the query to Phone Validation API and gives users a clear next step.

When to use it

Use this section when the list specifically needs Phone Validation API rather than a broad product overview.

What to check

Confirm input ownership, phone format, confidence, and the export segment needed downstream.

Where to go next

Open Phone Validation API or the related API page when this check should run at scale.