Phone Validation API validates the phone number and provides phone metadata, such as carrier name, line type (landline, mobile, non-fixed VoIP, etc.), is the phone prepaid, and includes a phone activity score to help identify disconnected phone numbers. Typical use cases for this phone validation API includes lead contactability and prioritization.
{
"id": "Phone.f6aa35da-0860-4122-9ab7-94d3409ac2d2",
"phone_number": "+17128475109",
"is_valid": true,
"activity_score": 30,
"country_calling_code": "1",
"country_code": "US",
"country_name": "United States",
"line_type": "Unknown",
"carrier": "Fibernetics - SVR",
"is_prepaid": false,
"error": null,
"warnings": []
}
curl --location --request GET 'https://zylalabs.com/api/3690/phone+validation+api/4164/phone+validation+api?phone=4259853735' --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 following checks are performed by Trestle's Phone Validation API: (1) Syntax Checks (2) Is the number assigned to a carrier? (3) Is the number connected or Disconnected? In addition, the API also provides country code, line typ (Landline, Mobile, Fixed and Non-fixed VoIP, Tollfree, etc.) and whether the phone is prepaid or not.
Trestle’s Phone Activity Scores range from 0 to 100. A score of 100 means consistent activity in the last 12 months, while a score of 0 means it is a disconnected number or no activity has been seen in the past 12 months. An activity score of 70 or above means there is high confidence that the phone is connected, assigned to a subscriber, and someone has been placing calls consistently. An activity score of 30 or below means there is high confidence that the phone is either disconnected, or no one will answer the call when the number is dialed. An activity score of 50 means Trestle doesn’t have enough signals to predict whether the phone is connected or disconnected and inactive.
The maximum QPS supported by this integration, is 10.
The Phone Validation API returns detailed metadata about phone numbers, including validation status, carrier information, line type, prepaid status, and an activity score. This data helps assess the connectivity and reliability of a phone number.
Key fields in the response include `is_valid`, `activity_score`, `carrier`, `line_type`, `is_prepaid`, `country_code`, and `country_name`. These fields provide essential insights into the phone number's status and characteristics.
The response data is structured in JSON format, with key-value pairs representing various attributes of the phone number. This format allows for easy parsing and integration into applications.
The API provides information on phone number validity, carrier details, line type (e.g., mobile, landline), prepaid status, and an activity score to indicate the likelihood of the number being connected.
The data is sourced from multiple telecommunications providers and databases, ensuring comprehensive coverage and accuracy. Regular updates and quality checks maintain data integrity.
Users can customize requests by specifying the phone number they wish to validate. The API accepts international formats, ensuring flexibility in input.
Typical use cases include lead validation for marketing campaigns, fraud prevention, customer onboarding, and improving contactability by identifying active phone numbers.
If the API returns partial or empty results, users should check the `is_valid` field. If false, the number may be invalid or disconnected. Users can implement fallback strategies, such as prompting for a new number.
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
Service Level:
100%
Response Time:
811ms
Service Level:
100%
Response Time:
181ms
Service Level:
100%
Response Time:
70ms
Service Level:
100%
Response Time:
254ms
Service Level:
100%
Response Time:
183ms
Service Level:
100%
Response Time:
1,455ms
Service Level:
100%
Response Time:
835ms
Service Level:
100%
Response Time:
117ms
Service Level:
100%
Response Time:
5,246ms
Service Level:
100%
Response Time:
913ms