The Mobile Number Checker API verifies, analyzes, and formats phone numbers worldwide with high accuracy. Its main purpose is to provide the ability to confirm the validity of a number before it is used in critical processes, such as user registrations, message deliveries, or authentication systems.
This API provides detailed information that goes beyond simple validation. For example, it determines whether a number is valid and belongs to a legitimate provider or whether it is a disposable number, which is essential for preventing fraud, fake accounts, or unreliable communications. In addition, it provides data on the associated network provider, such as China Mobile, as well as the geographic location (city, region, and country), allowing users to be segmented or specific filters to be applied in different regions.
The response includes country indicators such as the international code, ISO2 and ISO3 identifiers, and location on the continent, which is very useful data for standardization and integration processes in global systems. It also provides the corresponding time zone, making it easier to schedule communications at times that are convenient for each user.
In short, it is an essential tool for any company that wants to maintain a clean, secure, and up-to-date contact database, reducing the risk of fraud and optimizing the user experience in every interaction.
Verifica números em todo o mundo detecta uso descartável identifica provedores países regiões fusos horários e fornece formatos padronizados para comunicação consistente
{"is_valid":true,"is_disposable":false,"provider":"China Mobile","location":"Nanning, Guangxi","country":"China","country_iso2":"CN","country_iso3":"CHN","country_code":86,"continent":"Asia","time_zones":["Asia/Shanghai"],"format_national":"158 7879 9485","format_e164":"+8615878799485","format_international":"+86 158 7879 9485","format_rfc3966":"tel:+86-158-7879-9485"}
curl --location --request GET 'https://zylalabs.com/api/10139/mobile+number+checker+api/19452/verifica%c3%a7%c3%a3o+de+telefone&phone=Required' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Phone Check endpoint returns comprehensive data including the validity of the phone number, its provider, geographic location (city, region, country), time zone, and whether the number is disposable. This information helps in verifying user identities and preventing fraud.
Key fields in the response include "validity" (true/false), "provider" (network name), "location" (city, region, country), "timezone," and "disposable" (indicating if the number is temporary). These fields provide essential insights for user verification.
The response data is structured in a JSON format, with key-value pairs for each field. For example, you may see fields like "country_code," "provider," and "timezone" clearly delineated, making it easy to parse and utilize in applications.
The Phone Check endpoint provides information on number validity, associated network provider, geographic location, time zone, and whether the number is disposable. This data is crucial for ensuring reliable communication and user authentication.
The Phone Check endpoint accepts parameters such as "phone_number" for the number to be verified. Users can customize requests by specifying the format of the response or including additional filters based on geographic regions.
Data accuracy is maintained through regular updates from trusted telecommunications sources and validation checks against known databases. This ensures that the information provided is current and reliable for user verification.
Typical use cases include user registration verification, fraud prevention, targeted marketing based on geographic location, and ensuring reliable communication by filtering out disposable numbers. This enhances user experience and security.
Users can utilize the returned data by integrating it into their systems for real-time verification during user sign-ups, segmenting users based on location for targeted campaigns, and scheduling communications according to the provided time zone.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
99%
Response Time:
1,257ms
Service Level:
100%
Response Time:
995ms
Service Level:
100%
Response Time:
592ms
Service Level:
100%
Response Time:
928ms
Service Level:
100%
Response Time:
369ms
Service Level:
100%
Response Time:
1,461ms
Service Level:
100%
Response Time:
778ms
Service Level:
100%
Response Time:
3,091ms
Service Level:
100%
Response Time:
320ms
Service Level:
100%
Response Time:
1,452ms
Service Level:
100%
Response Time:
54ms
Service Level:
100%
Response Time:
40ms
Service Level:
100%
Response Time:
46ms
Service Level:
100%
Response Time:
40ms
Service Level:
100%
Response Time:
62ms
Service Level:
100%
Response Time:
39ms
Service Level:
100%
Response Time:
76ms
Service Level:
100%
Response Time:
58ms
Service Level:
100%
Response Time:
52ms
Service Level:
100%
Response Time:
8,351ms