The WhatsApp Validator API is an efficient and reliable tool designed to validate phone numbers registered on the WhatsApp platform. Its main function is to verify whether a specific phone number is active and enabled to receive messages via WhatsApp, which is essential for applications that rely on instant and secure communications with their users.
When a phone number is submitted, the API responds with key information including the JID (Jabber ID), a unique identifier representing the number within the WhatsApp system, the phone number in international format, and a confirmation message indicating whether the number is valid. It also returns an HTTP status code, usually 200, to indicate that the query was processed correctly.
This validation is essential to avoid errors in sending messages, ensure that marketing campaigns, notifications, or automated interactions are only directed to active numbers, and improve system efficiency by reducing the number of failed attempts. This optimizes service performance, improves the end-user experience, and prevents blocks or penalties for sending messages to non-existent or invalid numbers.
The API is easy to integrate into different platforms and programming languages, making it ideal for developers looking to add an additional layer of verification to their WhatsApp-based communication solutions. It also contributes to database cleaning and maintenance, ensuring that stored contacts are active and can be contacted effectively.
In short, the WhatsApp Validator API is an indispensable tool for quickly validating WhatsApp numbers, ensuring the quality of your data and the effectiveness of direct communication with your users or customers.
To use this endpoint, you must specify a phone number in the parameter.
Number Validation - Endpoint Features
Object | Description |
---|---|
phone |
[Required] Indicates a phone number |
{"Example Response":"No response example available for now."}
curl --location --request GET 'https://zylalabs.com/api/9316/whatsapp+validator+api/16825/number+validation?phone=+212612542343' --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 WhatsApp Validator API returns data including the Jabber ID (JID), the validated phone number in international format, a status indicating validity, and a confirmation message. This information helps confirm whether a number is active on WhatsApp.
The key fields in the response data include "jid" (Jabber ID), "number" (validated phone number), "status" (validity status), and "message" (confirmation message). These fields provide essential information for validating WhatsApp numbers.
The response data is structured in a JSON format, containing key-value pairs for easy parsing. Each response includes fields like "jid," "number," "status," and "message," allowing developers to quickly access the validation results.
The primary parameter for the WhatsApp Validator API is the phone number, which must be provided in international format. This ensures accurate validation and response from the API.
Typical use cases include validating phone numbers for marketing campaigns, ensuring automated notifications reach active users, and maintaining clean contact databases. This helps improve communication efficiency and reduces message failures.
Data accuracy is maintained through regular updates and checks against the WhatsApp platform. The API verifies the existence of phone numbers in real-time, ensuring that the information returned is current and reliable.
Users can utilize the returned data by checking the "status" field to determine if a number is valid. If valid, they can proceed with messaging or marketing efforts, while invalid numbers can be filtered out to enhance communication strategies.
Standard data patterns include a "status" of "valid" or "invalid," with corresponding messages that clarify the result. Users can expect consistent formatting in the response, facilitating easy integration into applications.
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.
To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
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 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
1,449.41ms
Service Level:
100%
Response Time:
3,074.18ms
Service Level:
100%
Response Time:
992.41ms
Service Level:
100%
Response Time:
1,222.08ms
Service Level:
91%
Response Time:
331.48ms
Service Level:
100%
Response Time:
661.90ms
Service Level:
60%
Response Time:
588.63ms
Service Level:
100%
Response Time:
3,539.67ms
Service Level:
100%
Response Time:
763.78ms
Service Level:
100%
Response Time:
524.20ms