Phone and Email Data Validation API

API ID 11267

Ensure accuracy with our Phone and Email Data Validation API for reliable contact information.

100% uptime 1,247 ms avg response

API Documentation

Endpoints

Request

Verify emails, validating format, domain, SMTP compatibility, MX records, and actual availability of the receiving server.

Endpoint ID: 21267
POST https://pr213-testing.zylalabs.com/api/11267/phone+and+email+data+validation+api/21267/validate+email
INPUT PARAMETERS

Validate Email — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{"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}}
Validate Email — CODE SNIPPETS

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]"
}'

    
Request

Validates phone numbers, confirming format, country, region, type, availability, international codes, and associated time zones correctly.

Endpoint ID: 21270
POST https://pr213-testing.zylalabs.com/api/11267/phone+and+email+data+validation+api/21270/phone+validation
INPUT PARAMETERS

Phone Validation — Endpoint Features

Object Description
Request Body Required Json

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

API EXAMPLE RESPONSE
JSON
{"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}
Phone Validation — CODE SNIPPETS

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"
}'

    

API Access Key & Authentication

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.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan
Custom Volume

  • Custom Rate Limit
  • Team & Access Management
  • SLA-backed Uptime
  • Specialized Customer Support
  • Real-Time API Monitoring
  • Enterprise Security & Compliance
Minimum annual contract: USD 10,000

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.

Phone and Email Data Validation API FAQs

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.

General FAQs

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.

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.

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.

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 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.

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.
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]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs


You might also like