With Phone Validator API you will be able to know if any of the numbers located on your database are valid or not. Also you will receive extra information about where it is that phone number as well.
Just pass the phone number you want to validate. Do not worry about country prefixes, the API will solve it automatically for you. After you pass the number you will receive information like the validity of that number, country, and also carrier company (Verizon, Movistar, Vodaphone, etc.).
This API is ideal to check what numbers on your database are valid. Use it to check what numbers are reachable before making an SMS campaign. Or, maybe, you want to sort your phone numbers database by country or company carrier to have a better approach to your customers.
The only limitation is the number of API calls you can make per month.
Use this endpoint to check the phone number's validity and its additional information.
Verification - Endpoint Features
Object | Description |
---|---|
text |
[Required] Phone number |
country |
[Required] |
{"nums":[{"isValid":true,"countryCode":"49","city":"Germany","msisdn":"4915123577723","national":"01512 3577723","international":"+49 1512 3577723","E164":"+4915123577723","carrier":"T-Mobile","country":"Germany","number_type":"MOBILE"}],"state":{"state":"done"}}
curl --location --request GET 'https://zylalabs.com/api/32/phone+number+validator+api/95/verification?text=+4915123577723&country=usa' --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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
The Phone Number Validator API allows you to validate phone numbers to determine if they are valid or not. It helps you verify the accuracy of phone numbers stored in your database. Additionally, the API provides additional information about the location associated with the phone number.
The Phone Number Validator API employs various techniques to validate phone numbers. It checks the format, length, and number type to determine if a phone number is valid. The API also performs checks against known phone number patterns and uses data from reputable sources to verify the accuracy of the provided phone number.
In addition to validating the phone number's validity, the API offers extra information about the location associated with the phone number. This information may include the country, city, state, and even geographical coordinates, depending on the data available for that specific phone number.
Integrating the Phone Number Validator API into your database or application is typically straightforward. The API usually follows a RESTful architecture, allowing you to make HTTP requests to its endpoints. You can pass the phone number you want to validate as a parameter in the API request, and it will respond with the validation result and additional location information.
No, at the moment bulk consults are not supported. You must make one API call per phone number that you want to validate.
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.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
947ms
Service Level:
99%
Response Time:
90ms
Service Level:
100%
Response Time:
168ms
Service Level:
100%
Response Time:
833ms
Service Level:
100%
Response Time:
433ms
Service Level:
100%
Response Time:
356ms
Service Level:
100%
Response Time:
233ms
Service Level:
100%
Response Time:
467ms
Service Level:
100%
Response Time:
586ms
Service Level:
100%
Response Time:
1,527ms
Service Level:
100%
Response Time:
1,166ms
Service Level:
100%
Response Time:
729ms
Service Level:
100%
Response Time:
569ms
Service Level:
100%
Response Time:
46ms
Service Level:
100%
Response Time:
277ms
Service Level:
100%
Response Time:
260ms
Service Level:
100%
Response Time:
3,074ms