Freedom251 › Phone Number Validation Software
OmaxTelecom Phone Validation API
What OmaxTelecom Phone Validation API is
OmaxTelecom Phone Validation API checks whether phone numbers are valid or possible and returns information such as line type, country, timezone, and carrier when available. Requests can use E.164 or national-format numbers with an ISO 3166-1 alpha-2 region code. The API can return normalized number formats, calling codes, geocoder details, time zones, and carrier data. It supports individual requests as well as asynchronous bulk jobs, with status polling for per-number results. Authentication uses OAuth 2.0 Client Credentials; bearer tokens expire after five minutes. An optional locale setting controls the language used for geocoder and carrier-name mapping. The vendor describes validation and enrichment as operating without live network queries. Businesses can use it for messaging, onboarding, routing, and list processing. The listed plan is €0.00 per once, with validation queries billed at €0.002 when the account’s price_per_validation is greater than zero; repeat checks are billed too. Monthly volume discounts begin at 10K validations. The API does not return MCC/MNC identifiers.
Who it suits
It suits businesses checking numbers for messaging, onboarding, routing, or large list processing. Customers needing MCC/MNC identifiers are directed to OmaxTelecom’s separate Number Lookup API.
What it does well
- Supports single-number and asynchronous bulk requests
- Returns line type, country, timezone, and carrier data
- Accepts E.164 and regional national-format numbers
- Public health endpoint requires no authentication
What to know first
- Does not return MCC/MNC identifiers
- Repeat validations are charged when the account rate is positive
- Bearer tokens expire after five minutes
Limits
The plan is listed as free, but accounts with a price_per_validation greater than zero are charged €0.002 per validation, including repeats. Monthly pricing is standard up to 10K validations, discounted 10% from 10K–100K and 20% from 100K–1M, with custom pricing above 1M.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Phone Validation API | €0.002 per validation query; single and bulk validations billed per request · All countries · up to 10K/month standard rates · 10K–100K/month 10% discount · 100K–1M/month 20% discount · 1M+/month custom pricing | Free |
As omaxtelecom.com lists them, read 9 Oct 2026. The maker's own page has the final word.
Getting started
- Open the OmaxTelecom Phone Validation website and API reference.
- Use the developer portal's integration-support email if support is needed.
- Authenticate with OAuth 2.0 Client Credentials and obtain a bearer token.
- Submit an E.164 number or a national-format number with its ISO 3166-1 alpha-2 region code.
- For multiple numbers, start an asynchronous bulk job and poll its status for results.
Verdict
OmaxTelecom Phone Validation API combines number validation with available carrier, location, and line-type metadata, and supports both single and bulk workflows. Check the billing terms and separate MCC/MNC limitation against your needs before integrating it.
Questions
What does OmaxTelecom Phone Validation API do?
It checks whether numbers are valid or possible and can return number formats, country, line type, geocoder, time zone, and carrier information when available.
How much does it cost?
The Phone Validation API plan is free. When the account's price_per_validation is greater than zero, each validation costs €0.002, including repeat validations.
Does it support bulk validation?
Yes. It supports asynchronous bulk jobs, with status polling for per-number results.
What authentication does it use?
It uses OAuth 2.0 Client Credentials with bearer tokens that expire after five minutes.
Does the API provide MCC/MNC?
No. Phone Validation does not return MCC/MNC; the vendor directs customers needing those identifiers to its separate Number Lookup API.
Does it query live phone networks?
The vendor describes validation and enrichment as operating without live network queries.
Facts from OmaxTelecom Phone Validation API's own pages
- Authentication
- The API uses OAuth 2.0 Client Credentials with bearer tokens that expire after five minutes. · omaxtelecom.com, 9 Oct 2026
- 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. · omaxtelecom.com, 9 Oct 2026
- Documentation and support
- The API reference provides schemas and examples, and the developer portal lists an integration-support email address. · developer.omaxtelecom.com, 9 Oct 2026
- Health check
- A public GET /phone-validation/health endpoint reports service availability and does not require authentication. · omaxtelecom.com, 9 Oct 2026
- Input formats
- Requests accept E.164 numbers or national-format numbers with an ISO 3166-1 alpha-2 region code. · omaxtelecom.com, 9 Oct 2026
- Intended users
- The vendor describes the API for businesses validating numbers for messaging, onboarding, routing, and high-volume list processing. · omaxtelecom.com, 9 Oct 2026
- Locale
- An optional locale parameter controls the language used for geocoder and carrier-name mapping. · omaxtelecom.com, 9 Oct 2026
- No live network query
- The vendor describes validation and enrichment as operating without live network queries. · omaxtelecom.com, 9 Oct 2026
- Notable limit
- Phone Validation does not return MCC/MNC; the vendor directs customers needing those network identifiers to its separate Number Lookup API. · omaxtelecom.com, 9 Oct 2026
- Purpose
- The API checks whether phone numbers are valid or possible and returns line type, country, timezone, and carrier name. · omaxtelecom.com, 9 Oct 2026
- 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. · omaxtelecom.com, 9 Oct 2026
- 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. · omaxtelecom.com, 9 Oct 2026
- Single and bulk
- The API supports single-number requests and asynchronous bulk jobs whose status can be polled for per-number results. · omaxtelecom.com, 9 Oct 2026
- 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. · omaxtelecom.com, 9 Oct 2026
Where OmaxTelecom Phone Validation API stands on Freedom251
- Phone Number Validation Software#21 of 25