API Dashboard
API ENDPOINTS
API Rate Limits
If you require an increase beyond the default rate limits, please contact our support team to discuss your needs.
API RATE LIMITING
Rate limits are in place to protect our customers and the platform while allowing us to provide you with the best accuracy and validation speed. While it’s not our intention, going over these limits may result in a temporary block. As such, we recommend that our customers and partners adhere to best practices and stay within these limits.
GENERAL RATE LIMITS
Bad requests to any endpoint (as an example, not including the email parameter in an API call) 100 times in 1 minute will result in a temporary block for 1 hour.
Requests to non-existent pages or endpoints 100 times in 2 minutes will result in a temporary block for 1 hour.
GETCREDITS V2
We allow a maximum of 80,000 requests per hour for the following endpoints:
api.zerobounce.net/v2/getcredits
api-us.zerobounce.net/v2/getcredits*
api-eu.zerobounce.net/v2/getcredits
Exceeding this limit results in a temporary block for 1 day.
Bad API key requests (200 times in 1 hour) to the following endpoints will result in a temporary block for 1 day:
api.zerobounce.net/v2/getcredits
api-us.zerobounce.net/v2/getcredits
api-eu.zerobounce.net/v2/getcredits
API VALIDATION V2
We allow a maximum of 80,000 requests in 10 seconds (validations) for the following endpoints:
api.zerobounce.net/v2/validate
api-us.zerobounce.net/v2/validate*
api-eu.zerobounce.net/v2/validate
Exceeding this limit results in a temporary block for 1 minute.
Bad API key requests (200 times in 1 hour) to the following endpoints will result in a temporary block for 1 hour:
api.zerobounce.net/v2/validate
api-us.zerobounce.net/v2/validate*
api-eu.zerobounce.net/v2/validate
GETAPIUSAGE V2
Bad requests (200 times in 1 hour) to the following endpoints will result in a temporary block for 1 hour:
api.zerobounce.net/v2/getapiusage
api-us.zerobounce.net/v2/getapiusage*
api-eu.zerobounce.net/v2/getapiusage
BULKAPI AND BULKAPI BATCH VALIDATE
We allow a maximum of (250 requests in 1 minute) for the bulkapi.zerobounce.net/ before temporarily blocking for 1 hour.
We allow a maximum of (30 requests in 1 minute) for the bulkapi.zerobounce.net/v2/validatebatch before temporarily blocking for 10 minutes.
Bad requests to bulkapi.zerobounce.net (200 times in 1 hour) will result in a temporary block for 1 hour.
BULKAPI UNKNOWN
Batch responses to bulkapi.zerobounce.net/v2/validate that contains over 20 unknown statuses (that are neither greylisted nor antispam) more than once per hour will temporarily block for 1 hour.
ACTIVITY V2
Bad API key requests (200 times in 1 hour)to the following endpoints will result in a temporary block for 1 hour:
api.zerobounce.net/v2/activity
api-us.zerobounce.net/v2/activity*
api-eu.zerobounce.net/v2/activity
- *This endpoint uses servers located within the United States. By utilizing this endpoint, you acknowledge and consent to your data being processed on servers in the United States.
API Error Codes
API Error Codes
We understand that things don’t always go well when making your first API call, especially when it’s your first time integrating with our API. Let’s look at the most common status codes that indicate an error response with a brief explanation:
Be advised - In June 2023, ZeroBounce added a security measure called API Shield. The API Shield is a dynamic security feature and may be enabled and disabled throughout the day based on traffic patterns, ongoing attacks, maintenance, and other factors. If the API Shield is enabled, you may sometimes receive a 403 Forbidden response, while when disabled, the API error codes below will be displayed. Please consider all these error codes as exceptions.
429 - Too Many Requests when such error occurs it is advised to consider throttling the requests as you’ve hit the rate limits. Also please refer to the API Rates Limit section in the documentation.
400 - Bad Requests in most cases this suggests that there is an error in your API request, please recheck the documentation.
404 - Not Found the most common error code, it simply means that the endpoint you are trying to reach does not exist on the API server, best will be to check for typos or recheck the documentation.
405 - Method Not Allowed this suggest you are trying to access a HTTP resource using an unsupported REST method (example, you are trying to do a GET on a POST endpoint), please recheck the documentation.
500 - Internal Server Error while highly unlikely, the error suggest a platform issue and you’ll need to contact support.
520 or 524 - Unexpected unknown error While highly unlikely, this suggests a transport error that may occur for a number of different reasons. We constantly monitor and address any and all 520/524 occurrences with our transit providers, and will be available to assist you. Please retry at your earliest convenience or contact our support team for more information.
TLS Support
WHY ARE WE ONLY SUPPORTING TLS 1.2 AND ABOVE?
The PCI Security Council sets the rules on which technologies are acceptable for use in transmitting cardholder data. They have explicitly identified TLS 1.0 as no longer being a strong form of encryption because it is vulnerable to many known attacks.
Almost every website has stopped supporting TLS 1.0 and 1.1, this is done to help safeguard your information.
ARE YOU AFFECTED?
If you don't use our API's then it's un-likely you will be affected unless you're using a really old browser and or operating system. To check to see if your computer/browser supports TLS 1.2 or higher please visit this link: https://www.ssllabs.com/ssltest/viewMyClient.html
API LIBRARY SUPPORT
If you have code that connects with the ZeroBounce API, you must ensure that it will continue to work after June 1, 2018. Each language and library is different, below are the more popular languages.
THESE LANGUAGES WILL NEED SIGNIFICANT CHANGES/UPGRADES IN ORDER TO WORK:
- Java 6u45 / 7u45
- .NET before 4.5 (does not support TLS 1.2)
- .NET 4.5 (must have settings changed to explicitly enable TLS 1.2)
- OpenSSL 0.9.8
- Most dynamic languages such as Ruby, PHP, & Python rely on the underlying operating system’s OpenSSL version. You can check it by running OpenSSL version. 1.0.1 in the minimum required.
- PHP 5.5.19 and up has support for TLS 1.2
You can test your connection with various tools and documentation found on the internet. Please keep in mind that we are not experts in every language or framework and so we aren’t able to test or fix your code for you.
LANGUAGE SPECIFIC INSTRUCTIONS
- .NET 4.6: TLS 1.2 is used automatically. No changes are necessary.
- .NET 4.5: The SecurityProtocolType needs to be changed to Tls12 (using the SecurityProtocol Setter)
- .NET 4.0: TLS 1.2 is supported, but there’s no named SecurityProtocolType enumeration. Use (SecurityProtocolType)3072.
- .NET 3 and below: Must be upgraded to 4.5
Support for TLS System Default Versions included in the .NET
BROWSER SUPPORT
The following browsers DO NOT support TLS 1.2 and will no longer work
- Google Chrome 29
- Firefox 26
- Internet Explorer 10
- Safari 8
- iOS 4
- Android 4
Dashboard Statistics
Need detailed info about your email validationⓘ API usage? You’ll find it in your API dashboard.
Your API Dashboard is located in your account off the left-hand menu. Every-time you make a call to the API, it will record the email validationⓘ results. This way, you can quickly see a big picture overview of your credits usage and your results. No emails are saved, just a count of the results.

In the API Dashboard, as seen above, you will have a drop-down the drill into the details of the invalids, do not mail, and unknown status codes. Also, you will be able to graph by daily or monthly trends to get a more in-depth look into your email validations. This gives you a better perspective on how ZeroBounce has helped improve your email list.

In the above image, I clicked on the status I didn't want to show, leaving just the trend of the invalids. To get further details about the invalid results, change the menu on top to “Invalids by Sub_Status.”

Now you can see the sub_status breakdown of the "Invalids" emails. It's a very powerful tool that allows you to see usage summary by day, months, and even years, with a visual representation of the health of the emails you are passing through the API.
API Keys Management

The API Keys page is where you can manage API access to your ZeroBounce account. On the API Keys page, you can create new API keys or you can edit or delete existing keys except, except for the Master Key.
ADD NEW API KEY:

Step 1:
To create a new API Key click on "+ Create a new API Key" on the top right of the page.

Step 2:
Type in the name you wish to give the key and make sure to set the "active state" of the key to either yes or no. The Whitelist IP can be configured through Edit Mode after you have created your key.

After creating the key, your new key would be listed like in the example below.

EDIT KEY:
Step 1:
To edit your API key status, click on the pencil icon on the right (see example below). Only Whitelist IP can be edited for the Master Key.

Step 2:
On the edit mode, you will be able to change the name and active state of your API key. You are also able to enter an IP or an IP Range to whitelist. You can add more than one IP or IP Range and they can be edited or deleted once added.

GENERATE NEW KEY:
Step 1:
You can regenerate a new key to replace the current one.

Step 2:
Click OK to process the changes or Cancel to exit.

DELETE KEY:
Step 1:
Except for the Master key, you can delete the additional keys if they are no longer used.

Step 2:
Click OK to delete the selected key or Cancel to exit.

NOTE:
If you have reached the maximum number of allowed API Keys specified in your account, you will not be able to add any additional key.

Approved Integration Vendors
Do you need a hands-on specialist integrating our API into your applications, web pages, signup forms, or registration screens?
Consider using one of the approved integration vendors listed below to assist you with the technical setup and testing. They've been vetted and are ready to lend a hand.
Contact information includes website, email, and phone number. Also listed is the language support offered by each vendor.

Company Name: LOGIMONK Technologies
Contact: Logimonk
Email: contact@logimonk.com
Website: https://www.logimonk.com/
Phone: +91 9425 807 843
Tech supported: All
Languages: English, Hindu
"At LOGIMONK, we treat every project as an obstacle, and we strive to do our best to overcome it. We've been in the industry for quite some time to understand the difference between delivery and perfection, and we prize the latter."

Contact: Catalin Chivulescu
Email: catalin.chivulescu@nxthost.com
Website: https://www.nxthost.com/
Languages: English, Romanian
"Our high skilled support department will meet your sophisticated requirements at any given moment."

Contact: Quixtec
Email: contactus@quixtec.com
Website: https://www.quixtec.com/
Phone: (425) 267-9025
Tech supported: Click Here to see tech supported
Languages: English, Spanish, German, Hindu
"Our goal is to provide all our clients, whether you are a new startup or a global powerhouse, with all the resources and expertise to deliver an amazing project."
Need more help integrating our email validation API into your platform? Our Customer Support specialists are here to help 24/7. They can guide you and answer any questions to help you make the most of the ZeroBounce API. Please drop us a line in the live chat, call us or send us an email at support@zerobounce.net.