About the API:
Introducing our Phone Lookup API—a robust solution that revolutionizes the way you gather information about phone numbers. Seamlessly retrieve comprehensive phone geolocalization and metadata, empowering your applications with a wealth of contextual data. From pinpointing the geographical location to extracting crucial metadata, this API ensures a thorough understanding of phone numbers within your system.
Unlock a world of possibilities by integrating this API into your applications, whether you're developing a location-based service, enhancing user verification processes, or enriching customer profiles. With the ability to access geolocalization data, you can tailor experiences based on users' locations, providing targeted and personalized services.
The Phone Lookup API is designed for simplicity and efficiency, enabling developers to effortlessly incorporate it into their projects. Stay ahead in a data-driven world, where every phone number holds valuable insights waiting to be unveiled. Whether you're safeguarding user interactions or optimizing your business strategies, our Phone Lookup API is the key to unlocking the potential of phone geolocalization and metadata retrieval, ushering in a new era of precision and intelligence for your applications.
Pass the phone number with the country code and receive the location and metadata.
Location-Based Services: Use Case: Integrate the Phone Lookup API into location-based services such as delivery apps or local business directories. Retrieve geolocalization data to enhance user experiences by tailoring content, promotions, or services based on the user's location, offering a personalized touch.
Fraud Prevention and User Verification: Use Case: Strengthen fraud prevention measures by incorporating the Phone Lookup API into user verification processes. Validate user-provided phone numbers by cross-referencing geolocalization and metadata, ensuring authenticity and mitigating risks associated with fake accounts or unauthorized access.
Customer Relationship Management (CRM): Use Case: Enrich customer profiles within CRM systems by utilizing the Phone Lookup API. Obtain geolocalization insights and additional metadata associated with phone numbers to create a comprehensive view of customers. This aids in targeted communication, improved segmentation, and personalized customer interactions.
Emergency Services and Public Safety: Use Case: Enhance emergency response systems by integrating the Phone Lookup API to quickly identify the location associated with distress calls. Geolocalization data aids in dispatching services efficiently, reducing response times, and improving the overall effectiveness of emergency services.
Marketing and Campaign Optimization: Use Case: Improve the efficiency of marketing campaigns by leveraging the Phone Lookup API to gather geolocalization and metadata. Tailor marketing strategies based on regional preferences, optimizing ad targeting and content delivery for a more impactful and localized marketing approach.
Besides API call limitations per month, there are no other limitations.
Pass the phone number with its country code and receive its location and metadata.
Get Data - Endpoint Features
Object | Description |
---|---|
number |
[Required] Phone number. |
{"only_number":"2069735100","phone_number":"+12069735100","possible":"True","r_format":"+1-206-973-5100","region":"1","region_code":"US","service_provider":"","state":"Washington State","timezone_details":"America/Los_Angeles","valid":"True"}
curl --location --request GET 'https://zylalabs.com/api/3221/phone+lookup+api/3447/get+data?number=12069735100' --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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
The API uses a combination of telecom infrastructure data and proprietary algorithms to determine the geolocalization of a phone number. This includes information such as the associated cell tower, network data, and geographical databases.
The API provides a range of metadata, including carrier information, line type (mobile or landline), and region-specific details. Additional data may include the phone number's status, porting history, and any associated information available from authoritative sources.
Yes, the API adheres to privacy regulations and operates within the boundaries of applicable laws. It focuses on providing publicly available and non-sensitive information associated with phone numbers while prioritizing user privacy and data security.
Yes, the Phone Lookup API is designed to support real-time phone number validation. Developers can integrate this feature into applications to instantly verify and authenticate user-provided phone numbers, ensuring accurate and up-to-date information.
Yes, the Phone Lookup API supports international phone numbers. It provides geolocalization and metadata for phone numbers globally, allowing for seamless integration into applications with an international user base.
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, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
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 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
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]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
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 trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
100%
Response Time:
268ms
Service Level:
100%
Response Time:
1,436ms
Service Level:
100%
Response Time:
599ms
Service Level:
100%
Response Time:
694ms
Service Level:
100%
Response Time:
723ms
Service Level:
100%
Response Time:
744ms
Service Level:
100%
Response Time:
569ms
Service Level:
100%
Response Time:
303ms
Service Level:
100%
Response Time:
990ms
Service Level:
100%
Response Time:
220ms
Service Level:
100%
Response Time:
355ms
Service Level:
100%
Response Time:
580ms
Service Level:
100%
Response Time:
649ms
Service Level:
100%
Response Time:
1,627ms
Service Level:
100%
Response Time:
729ms
Service Level:
100%
Response Time:
320ms
Service Level:
100%
Response Time:
486ms