Cut Wasted SMS Spend
Reject invalid numbers before sending. Reduce failed deliveries and lower messaging costs on every campaign.
Phone Validation API
Phone Number Validation API.
From €0.002/query.
Check valid and possible numbers, line type, country, timezone, and carrier name. E.164 or national format with region.
REST API with OAuth 2.0 authentication. Single lookups or async bulk jobs. One global price for all countries.
€0.002/query All countries E.164 or national
$ curl -X POST https://api.omaxtelecom.com/numbers/phone-validation \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+38766000111"
}'
// Response
{
"success": true,
"data": {
"valid": true,
"possible": true,
"phone_number": "+38766000111",
"national_format": "066 000-111",
"country_code": "BA",
"number_type": "MOBILE",
"carrier": { "name": "BH Telecom" }
}
}Use Cases
What You Can Do with Phone Validation API
Validate and enrich phone numbers before messaging, onboarding, or routing — without live network queries.
Form & KYC Screening
Validate numbers at sign-up. Flag impossible or malformed inputs before they enter your database.
Clean CRM & Contact Lists
Normalize and enrich contact databases before campaigns. Remove stale entries and improve data quality.
Improve OTP Delivery
Confirm a number is valid and correctly formatted before sending verification codes. Fewer retries, higher conversion.
Route by Number Type
Distinguish mobile from fixed-line numbers. Apply different logic for SMS, voice, or compliance workflows.
Bulk List Hygiene
Queue async bulk validation jobs for large datasets. Per-number results with status tracking until the job completes.
Response
What You Get Back
Every validation returns structured metadata you can use in forms, CRMs, and routing logic.
valid
Whether the number is valid for the detected region.
possible
Whether the number could become valid with more digits.
phone_number
Normalized E.164 format (e.g. +38766000111).
national_format
National formatting for display (e.g. 066 000-111).
country_code
ISO 3166-1 alpha-2 country code (e.g. BA).
calling_code
International calling code without plus (e.g. 387).
number_type
Line type such as MOBILE, FIXED_LINE, or UNKNOWN.
geocoder
Geographic description and locale for the number region.
time_zones
Associated time zones (e.g. Europe/Sarajevo).
carrier
Carrier name and locale when available from numbering data.
Line types
Number Types Returned
Documented number_type values from the API response.
MOBILE
Mobile handset numbers suitable for SMS and OTP delivery workflows.
FIXED_LINE
Landline numbers — useful for routing voice or excluding from SMS sends.
UNKNOWN
Returned when line type cannot be determined from the input or numbering plan.
Platform
Features
Developer-friendly REST API built for real-time validation and high-volume batch processing.
E.164 or National Input
Accept international E.164 numbers or national format with an ISO region code. No pre-normalization required.
Locale-Aware Metadata
Optional locale parameter for geocoder and carrier name mapping in your preferred language.
Async Bulk Jobs
Queue bulk validation jobs with multiple numbers per request. Poll for results when the job completes.
OAuth 2.0 Client Credentials
Secure authentication via RFC 6749 Client Credentials grant. Bearer tokens with 5-minute expiry.
One Global Price
€0.002 per validation across all countries. No per-destination rate tables or hidden surcharges.
Health Endpoint
Public service health check at GET /phone-validation/health. No authentication required.
Integration
How It Works
Three steps from Console enablement to validation at scale.
01
Enable & Get Credentials
Enable Phone Validation in the OmaxTelecom Console and obtain your Client ID and Client Secret. Self-service credentials in minutes.
02
Authenticate & Validate
Exchange credentials for a Bearer token via OAuth 2.0 Client Credentials. POST a single number or queue a bulk validation job.
03
Scale with Bulk Jobs
Submit multiple numbers in one bulk request. Poll job status until completed and retrieve per-number validation results.
Compare
Phone Validation vs Number Lookup
Two complementary APIs — choose validation for format and metadata, lookup for carrier network data.
| Capability | Phone Validation | Number Lookup |
|---|---|---|
| Primary use | Format & metadata validation | Carrier network lookup |
| Input format | E.164 or national + region | E.164 only |
| Valid / possible flags | Yes | No |
| Line type | MOBILE, FIXED_LINE, UNKNOWN | mobile / landline |
| MCC / MNC | No | Yes |
| Geocoder & time zones | Yes | No |
| Price per query | €0.002 | €0.0065 |
| Bulk jobs | Async job polling | Async job polling |
Need MCC/MNC? See Number Lookup API.
Rates
€0.002 per Validation, All Countries
One flat rate worldwide. No per-destination tables. Volume discounts for high-throughput integrations.
€0.002
per validation query
Same price for every country. Single and bulk validations billed per request.
Up to 10K/month
Standard rates
10K–100K/month
10% discount
100K–1M/month
20% discount
1M+/month
Custom pricing
Each request is charged when price_per_validation is greater than zero. Contact us for custom volume pricing above 1M queries per month.
Quick Start - Your First Validation
A single API call returns validity, line type, and carrier metadata.
$ curl -X POST https://api.omaxtelecom.com/numbers/phone-validation \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+38766000111"
}'
// Response
{
"success": true,
"data": {
"valid": true,
"number_type": "MOBILE",
"carrier": { "name": "BH Telecom" }
}
}Full API reference at developer.omaxtelecom.com
FAQ
Frequently Asked Questions
The Phone Validation API uses OAuth 2.0 Client Credentials (RFC 6749 §4.4). Exchange your Client ID and Client Secret from the OmaxTelecom Console for a Bearer access token at POST /auth/token. Include the token in the Authorization header for all validation requests.
Phone Validation checks whether a number is valid and returns format metadata — line type, country, timezone, geocoder, and carrier name. Number Lookup returns live carrier data including MCC and MNC for E.164 numbers. Use Phone Validation for form checks and list hygiene; use Number Lookup when you need network identifiers for routing.
You can submit E.164 format (e.g. +38766000111) or national format. For national numbers, include the region field as an ISO 3166-1 alpha-2 country code (e.g. BA). Optional locale controls geocoder and carrier name mapping.
The API returns HTTP 200 with success: true and data containing valid: false and possible: false. You still receive normalized fields where available, such as country_code and number_type: UNKNOWN.
Each validation is charged at €0.002 when price_per_validation is greater than zero. Billing applies per request, including repeat validations of the same number. Volume discounts are available at 10K+, 100K+, and 1M+ queries per month.
POST /phone-validation/bulk with a validations array returns 202 Accepted and a job_id. Poll GET /phone-validation/bulk/{job_id} until status is completed or failed. Each item includes its own result or error.
Yes. GET /phone-validation/health is a public endpoint that returns service availability. No authentication is required.
Complete documentation including request/response schemas is available at developer.omaxtelecom.com/api/phone-validation. You can also sign up at console.omaxtelecom.com to enable the API and get credentials.
Integrate via Phone Validation API
Start validating phone numbers with our REST API. Clear documentation, OAuth 2.0 auth, and developer support.
Phone Validation API Setup
Get a personalised walkthrough of our phone validation API, pricing, and integration process.
- API credentials and Console enablement
- Single and bulk validation walkthrough
- Volume pricing for your use case
- Live Q&A with our team
No credit card required · Setup in 48 hours · Cancel anytime
Prefer email? [email protected]
Related Products
Number Lookup API
Live carrier lookup with MCC/MNC for E.164 numbers. From €0.0065/query when you need network identifiers.
Learn moreEnterprise SMS
Send promotional, transactional, and 2FA/OTP messages worldwide. Validate numbers before sending.
Learn moreWholesale DIDs
Virtual phone numbers from around the world. Instant provisioning, flexible SIP routing, and SMS-enabled options.
Learn more