Phone Verify API is an advanced tool designed to validate and verify phone numbers in real-time, providing users with a robust solution to ensure the accuracy of contact data in their systems. This API is ideal for applications that require rigorous phone number verification, whether for account creation, user authentication, contact management or any other process that relies on accurate contact data. This verification is for US and Canada only.
Phone Verify API validates phone numbers to ensure they follow the standard format according to international standards. This includes checking the length of the number, the country code format and the structure of the number itself. The API can identify numbers belonging to testing services or temporary numbers used for fraud or unwanted activities. This helps maintain the integrity of databases and prevents the inclusion of incorrect data.
Phone Verify API provides information about the geographic location of the phone number, including country and city, if available. This feature is useful for personalising interactions with users based on their location, it also distinguishes between mobile and landline numbers, allowing users to tailor their communication and marketing strategies according to the type of number. It provides information about the operator of the phone number, which can be useful for segmentation and analysis purposes. This also helps to identify the network to which the number belongs, providing more context for communication.
The Phone Verify API receives phone numbers and provides format validation, spoof detection, location and operator details.
User Registration Validation: Verifies the validity of the phone number entered during registration on a website or app.
Two-Factor Authentication (2FA): Sends a verification code to the phone number to confirm identity during login.
Account Creation Fraud Prevention: Detects suspicious patterns in phone numbers to prevent fraud when creating new accounts.
CRM Contact Data Update: Verifies and updates the validity of customer phone numbers in a CRM system.
Financial Transaction Authentication: Confirm transactions by sending a code to the phone number associated with the transaction.
Basic Plan: 150 requests per day.
Pro Plan: 1300 requests per day.
Pro Plus Plan: 3000 requests per day.
To use this endpoint, send a request with the phone number in the body. You will receive the validity and details of the number in the response.
Check Phone - Endpoint Features
| Object | Description |
|---|---|
subscriber |
[Required] The 10 digit US/Canada subscriber phone number |
optIp |
Optional The ipv4 or ipv6 address of the opt-in subscriber will be used for geographic lookup if provided. |
optDate |
Optional Date in ISO 8601 format. The approximate date when this subscriber opted into the service will be used for our intelligent recommendation engine. For example, if a phone number has been temporarily suspended between optDate and the current date, the “action” recommendation in the API response will be “wait”. |
{"subscriber":"8182925409","optDate":"2024-08-15T18:55:56.532Z","action":"send","deliverable":"true","nanpType":"mobile","blackList":"false","ipResult":"valid-v4","dip":"success","dipLrn":"8182925409","dipPorted":"false","dipOcn":"6010","dipCarrier":"AT&T Mobility","dipCarrierSubType":"WIRELESS","dipCarrierType":"mobile","geoCountry":"US","geoState":"CA","geoCity":"Victorville","geoMetro":803,"geoSource":"ip","timezone":"America/Los_Angeles","tzOffset":8}
curl --location --request GET 'https://zylalabs.com/api/5021/phone+verify+api/6349/check+phone?subscriber=8182925409&optIp=172.95.90.55&optDate=2024-08-15T18:55:56.532Z' --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.
To use the API, make a GET request with the phone number as a parameter in the URL. The API will return validation, location, type and operator of the number.
The Phone Verify API validates phone numbers in real time, verifying format, location, type (mobile/fixed) and the associated operator. For USA and Canada only.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
The API returns detailed information about the age and history of a domain, including years, months and days since its creation, as well as expiration and update dates.
The Phone Verify API returns data including the validity of the phone number, its type (mobile or landline), geographic location (country, state, city), operator details, and additional flags like blacklist status and spoof detection.
Key fields in the response include "deliverable" (validity), "nanpType" (number type), "geoCountry" (country), "geoState" (state), "geoCity" (city), and "dipCarrier" (operator), providing comprehensive insights into the phone number.
The response data is structured in JSON format, with key-value pairs representing various attributes of the phone number. For example, "geoCity" provides the city name, while "dipCarrier" indicates the service provider.
The API provides information on phone number validity, geographic location, type (mobile or landline), operator details, and flags for testing or temporary numbers, enhancing data accuracy for user interactions.
Data accuracy is maintained through real-time validation checks against established standards, including format verification and identification of temporary or fraudulent numbers, ensuring reliable contact information.
Typical use cases include user registration validation, two-factor authentication, fraud prevention during account creation, and updating CRM contact data, ensuring accurate and reliable phone number information.
Users can utilize the returned data to personalize communication strategies, segment users based on number type or location, and enhance security measures by validating phone numbers during critical processes.
Standard data patterns include valid phone numbers with specific formats, identifiable mobile or landline types, and geographic information that aligns with the number's area code, aiding in effective data management.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
37ms
Service Level:
100%
Response Time:
89ms
Service Level:
100%
Response Time:
394ms
Service Level:
100%
Response Time:
681ms
Service Level:
100%
Response Time:
778ms
Service Level:
100%
Response Time:
901ms
Service Level:
100%
Response Time:
7,555ms
Service Level:
100%
Response Time:
550ms
Service Level:
100%
Response Time:
1,641ms
Service Level:
100%
Response Time:
605ms
Service Level:
100%
Response Time:
1,485ms
Service Level:
100%
Response Time:
596ms
Service Level:
100%
Response Time:
1,455ms
Service Level:
100%
Response Time:
130ms
Service Level:
100%
Response Time:
172ms
Service Level:
100%
Response Time:
4,446ms
Service Level:
100%
Response Time:
1,452ms
Service Level:
100%
Response Time:
417ms
Service Level:
100%
Response Time:
443ms
Service Level:
100%
Response Time:
315ms