{"valid":true,"metadata":{"local_part":"alexanderryan","domain":"gmail.com","ascii_email":"[email protected]","smtputf8":false,"mx":[[5,"gmail-smtp-in.l.google.com"],[10,"alt1.gmail-smtp-in.l.google.com"],[20,"alt2.gmail-smtp-in.l.google.com"],[30,"alt3.gmail-smtp-in.l.google.com"],[40,"alt4.gmail-smtp-in.l.google.com"]],"mx_records":true}}
curl --location --request POST 'https://pr213-testing.zylalabs.com/api/11267/phone+and+email+data+validation+api/21267/validate+email' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"email": "[email protected]"
}'
{"is_valid":true,"is_formatted_properly":true,"country":"United States","location":"Washington State","timezones":["America/Los_Angeles"],"format_national":"(206) 555-0111","format_international":"+1 206-555-0111","format_e164":"+12065550111","country_code":1,"region_code":"US","type":2,"possible":true,"national_number":2065550111}
curl --location --request POST 'https://pr213-testing.zylalabs.com/api/11267/phone+and+email+data+validation+api/21270/phone+validation' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"phone_number": "+12065550111"
}'
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 Phone and Email Data 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 Phone and Email Data Validation API accurately and reliably validates user contact information, including phone numbers and email addresses, ensuring that the data is correct, complete, and properly formatted. In the case of phone numbers, the endpoint verifies their validity, determining whether the number is real and possible, and whether it complies with both national and international formatting standards. It provides standardized versions of the number, including the national, international, and E.164 standard formats, facilitating its use in global communication systems. In addition, it identifies the country associated with the number, the region or state, and the corresponding time zones, offering additional contextual information that can be useful for applications that handle schedules, message delivery, or automatic calls. It also classifies the type of number, such as landline, mobile, or other, and provides country and region codes that allow for easier integration with international databases and systems.
For email addresses, it performs a thorough validation that includes verifying the correct format, the existence of the domain, and the server's ability to receive emails through active MX records. The structure of the address is analyzed, separating the local part and the domain, and an ASCII version of the email is provided for compatibility with different systems. It also indicates whether the email supports SMTP UTF-8 encoding, which may be relevant for multilingual messages. The returned MX records allow the delivery route to be checked and ensure that the email can be received effectively. This validation helps reduce errors, prevent failed deliveries, and improve the quality of contact databases.
Together, it offers a complete solution for contact data management and verification, ensuring that both phone numbers and emails are valid, possible, correctly formatted, and functional, allowing users to optimize communications and improve the user experience.
The Phone Validation endpoint returns data about the phone number's validity, format, country, region, type, and time zones. The Email Validation endpoint provides information on the email's validity, format, domain existence, SMTP compatibility, and MX records.
Key fields for the Phone Validation response include `is_valid`, `country`, `location`, and formatted numbers. For Email Validation, important fields are `valid`, `local_part`, `domain`, and `mx_records`.
The returned data is structured in JSON format. For example, the Phone Validation response includes nested objects for metadata, while the Email Validation response contains arrays for MX records, ensuring easy parsing and integration.
The Phone Validation endpoint provides information on number validity, formatting, country, region, type, and time zones. The Email Validation endpoint offers details on format, domain existence, SMTP compatibility, and MX records.
The response data is organized into key-value pairs, with top-level fields indicating overall validity and nested objects or arrays providing detailed information, such as MX records for emails or formatted numbers for phones.
The data is sourced from telecommunications databases and email service providers, ensuring comprehensive coverage and accuracy. Regular updates and checks are performed to maintain data quality.
Typical use cases include verifying user contact information during account creation, enhancing marketing campaigns by ensuring valid contact details, and improving customer support by confirming active communication channels.
Users can utilize the returned data to filter out invalid contacts, segment audiences based on region or type, and automate communication processes, ensuring messages reach valid and active addresses or numbers.
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