Secure Phone Validation API is a telephone validation service designed to offer comprehensive number verification on a global scale. Its main function is to analyze the structure of each number entered and determine whether it complies with the international formats defined by telecommunications authorities. This system identifies the country code, the type of line (whether mobile, landline, VoIP, among others), and evaluates the structural validity of the number, allowing companies to have accurate and up-to-date information about their contact records.
When the is_valid_structure field is false, the system indicates that the number does not fully comply with the expected standards for that format. This may be due to errors in length, incomplete prefixes, additional digits, or a structure that is incompatible with international standards. Even so, the query can be considered successful if the value success:true is present, which means that the service processed the information correctly and returned a reliable result.
In summary, Secure Phone Validation API offers a robust and automated solution for the verification, classification, and validation of international telephone numbers, ensuring database integrity, operational reliability, and greater effectiveness in global communication.
Validates international phone numbers by verifying structure, line type, and country, providing accurate and reliable results for integrations and systems.
Phone Validation - Endpoint Features
| Object | Description |
|---|---|
phone_number |
[Required] Enter a phone number |
{"success":true,"validation":{"is_valid_structure":false,"country_code":"33","country_name":"France","line_type":"Mobile","query_number":"+336730922"}}
curl --location --request GET 'https://zylalabs.com/api/11228/secure+phone+validation+api/21225/phone+validation?phone_number=+336730922' --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 Validation endpoint returns data that includes the validation status of the phone number, country code, country name, line type, and the original query number. This information helps users understand the validity and classification of the provided phone number.
The key fields in the response data include `success`, `is_valid_structure`, `country_code`, `country_name`, `line_type`, and `query_number`. These fields provide insights into the validation process and the characteristics of the phone number.
The response data is organized in a JSON format. The top-level field `success` indicates if the request was processed correctly, while the `validation` object contains detailed information about the phone number's validity, including its structure and classification.
The Phone Validation endpoint provides information on the validity of the phone number's structure, the country it belongs to, the type of line (mobile, landline, VoIP), and the original number queried. This comprehensive data aids in effective communication strategies.
Data accuracy is maintained through regular updates and adherence to international telecommunications standards. The API verifies numbers against established formats and classifications, ensuring reliable validation results for users.
Typical use cases include verifying customer contact information, ensuring compliance with communication regulations, enhancing marketing outreach, and maintaining database integrity. Businesses can use this data to improve customer engagement and reduce communication errors.
Users can utilize the returned data by checking the `is_valid_structure` field to determine if the number is valid. They can also analyze the `line_type` and `country_code` to tailor communication strategies based on the type of contact and geographical location.
Standard data patterns include a boolean `success` field indicating the request's outcome, and a `validation` object that may show `is_valid_structure` as true or false. Users should expect consistent formatting for country codes and line types across different queries.
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, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
377ms
Service Level:
100%
Response Time:
10,296ms
Service Level:
100%
Response Time:
377ms
Service Level:
100%
Response Time:
781ms
Service Level:
100%
Response Time:
377ms
Service Level:
100%
Response Time:
435ms
Service Level:
100%
Response Time:
311ms
Service Level:
100%
Response Time:
835ms
Service Level:
100%
Response Time:
184ms
Service Level:
100%
Response Time:
1,157ms
Service Level:
100%
Response Time:
537ms
Service Level:
100%
Response Time:
1,895ms
Service Level:
100%
Response Time:
2,923ms
Service Level:
100%
Response Time:
3,659ms
Service Level:
100%
Response Time:
1,906ms
Service Level:
100%
Response Time:
6,033ms
Service Level:
100%
Response Time:
942ms
Service Level:
100%
Response Time:
2,124ms
Service Level:
100%
Response Time:
0ms
Service Level:
100%
Response Time:
2,638ms