OmaxTelecom Phone Validation API
omaxtelecom.com
- API
What OmaxTelecom Phone Validation API is
OmaxTelecom Phone Validation API checks whether phone numbers are valid or possible, then returns available details such as line type, country, timezone and carrier. It accepts E.164 numbers or national-format numbers paired with an ISO 3166-1 alpha-2 region code. Responses may include normalized E.164 and national formats, country and calling codes, geocoder data, time zones and carrier information. You can validate one number or submit an asynchronous bulk job and poll its status for individual results. OAuth 2.0 Client Credentials authentication uses bearer tokens that expire after five minutes. An optional locale sets the language for geocoder and carrier-name mapping. The vendor describes validation and enrichment as working without live network queries. Listed uses include SMS cost reduction, sign-up and KYC screening, CRM cleanup, OTP delivery and routing by number type. The API is available for businesses handling messaging, onboarding, routing and high-volume lists. A public health endpoint reports availability without authentication.
Who it suits
It suits businesses validating numbers for messaging, onboarding, routing, KYC screening or large list processing. Developers can use its API and asynchronous bulk jobs in automated workflows.
Good to know, and what to watch
- Accepts E.164 and national-format inputs
- Supports asynchronous bulk validation jobs
- Returns line type and carrier data
- OAuth 2.0 bearer-token authentication
- Public unauthenticated health endpoint
- Does not return MCC/MNC identifiers
- Bearer tokens expire after five minutes
- Repeat validations can be billed
- No live network query is used
Plans
Every plan and pricePhone Validation API
From €0.00
The verdict
OmaxTelecom Phone Validation API combines number checking, metadata enrichment and bulk processing for business workflows. Review the per-validation billing and the missing MCC/MNC data before choosing it.
What the maker publishes
- Authentication
- The API uses OAuth 2.0 Client Credentials with bearer tokens that expire after five minutes. source
- Billing detail
- Each validation is charged at €0.002 when the account's price_per_validation is greater than zero, including repeat validations of the same number. source
- Documentation and support
- The API reference provides schemas and examples, and the developer portal lists an integration-support email address. source
- Health check
- A public GET /phone-validation/health endpoint reports service availability and does not require authentication. source
- Input formats
- Requests accept E.164 numbers or national-format numbers with an ISO 3166-1 alpha-2 region code. source
- Intended users
- The vendor describes the API for businesses validating numbers for messaging, onboarding, routing, and high-volume list processing. source
- Locale
- An optional locale parameter controls the language used for geocoder and carrier-name mapping. source
- No live network query
- The vendor describes validation and enrichment as operating without live network queries. source
- Notable limit
- Phone Validation does not return MCC/MNC; the vendor directs customers needing those network identifiers to its separate Number Lookup API. source
- Purpose
- The API checks whether phone numbers are valid or possible and returns line type, country, timezone, and carrier name. source
- Returned metadata
- Responses can include normalized E.164 and national formats, country and calling codes, line type, geocoder, time zones, and carrier information when available. source
- Security
- The company's privacy policy says it processes personal data in compliance with UK GDPR and the Data Protection Act 2018 and does not sell personal data to third parties. source
- Single and bulk
- The API supports single-number requests and asynchronous bulk jobs whose status can be polled for per-number results. source
- Use cases
- The vendor identifies SMS cost reduction, sign-up and KYC screening, CRM list cleanup, OTP delivery, and routing by number type as use cases. source
Checked against the maker's pages on 9 Oct 2026.