{"is_valid":true,"is_disposable":false,"provider":"Sunrise","location":"Switzerland","country":"Switzerland","country_iso2":"CH","country_iso3":"CHE","country_code":41,"continent":"Europe","time_zones":["Europe/Zurich"],"format_national":"077 236 40 31","format_e164":"+41772364031","format_international":"+41 77 236 40 31","format_rfc3966":"tel:+41-77-236-40-31","line_type":"mobile","is_mobile":true,"is_possible":true,"national_number":"772364031","country_flag":"🇨🇭","currency_code":"CHF","utc_offset":"+02:00"}
curl --location --request GET 'https://zylalabs.com/api/13118/international+phone+number+validation+api/26599/validator?phone=41772364031' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the International Phone Number Validation API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The International Phone Number Validation API helps developers verify and analyze phone numbers from countries around the world through a fast, reliable, and easy-to-integrate service. Rather than relying on basic format validation, the API provides detailed information that helps determine whether a phone number has the correct structure, is valid within its national numbering plan, and is associated with a valid telecommunications carrier.
With a single request, the API can identify the country, ISO country codes, international prefix, continent, local time zone, currency, and both national and international formats. It also detects the carrier or provider, determines whether the number belongs to a mobile or landline network, and indicates whether it is a disposable number, provided that information is available.
The API returns standardized formats, including E.164, international, national, and RFC3966 representations, which facilitate the consistent storage, display, and processing of phone numbers across different applications and systems.
The Validator endpoint returns comprehensive data about phone numbers, including validation status, carrier information, country details, formatting options, line type, mobile status, timezone, and currency. This allows users to assess the validity and characteristics of a phone number effectively.
Key fields in the response include `is_valid`, `provider`, `location`, `country`, `format_national`, `format_e164`, `line_type`, and `is_mobile`. These fields provide essential insights into the phone number's validity and associated details.
The returned data is structured in JSON format, featuring key-value pairs. For example, a valid response includes fields like `is_valid`, `country`, and various formatting options, making it easy to parse and integrate into applications.
The Validator endpoint provides information on phone number validity, carrier detection, country identification, line type (mobile or landline), timezone, and formatting options. This comprehensive data aids in effective phone number management.
The response data is organized in a JSON object, with each field representing a specific attribute of the phone number. For instance, fields like `is_valid` and `provider` are clearly defined, allowing for straightforward interpretation and use in applications.
The data is sourced from reliable telecommunications databases and national numbering plans. This ensures that the information provided is accurate and up-to-date, enhancing the reliability of the validation process.
Typical use cases include validating user-submitted phone numbers during registration, ensuring compliance with telecommunications regulations, and enhancing customer relationship management by verifying contact information.
Users can utilize the returned data to filter valid phone numbers, customize user experiences based on location, and integrate carrier information into their systems. For example, businesses can tailor marketing strategies based on the identified carrier or region.
The Validator endpoint accepts a phone number as a parameter, typically in international format. Users can customize their requests by including additional parameters for specific data points, such as carrier detection or formatting preferences, if supported.
The API covers phone numbers from countries worldwide, providing detailed information on various regions, including country codes, continents, and local time zones. This global coverage ensures comprehensive validation for international phone numbers.
Key fields include `is_valid` (indicates if the number is valid), `provider` (the telecommunications carrier), `line_type` (mobile or landline), and `is_disposable` (whether the number is temporary). Each field provides critical insights for effective phone number management.
Data accuracy is maintained through regular updates from reliable telecommunications databases and adherence to national numbering plans. This ensures that the information provided is current and trustworthy for validation purposes.
If the API returns partial or empty results, users should check the `is_valid` field. If it’s false, the number may be invalid. Users can implement error handling to prompt re-entry or provide alternative contact methods based on the response.
Quality checks include validation against national numbering plans and cross-referencing with telecommunications databases. This multi-layered approach helps ensure the reliability and accuracy of the data returned by the API.
Standard data patterns include structured JSON responses with fields like `format_national`, `format_e164`, and `time_zones`. Users can expect consistent formatting across different requests, facilitating easier integration into applications.
Users can customize requests by specifying the phone number in various formats and potentially including additional parameters for specific data points. This flexibility allows for tailored responses based on user needs and application requirements.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund