Docs
Docs
A 403 forbidden error can occur for a variety of reasons when using the ZeroBounce email service API. However, the most likely reason is that you're in violation of the Web Application Firewall (WAF) rules when using ZeroBounce API endpoints.
A 403 Forbidden error is an HTTP status response code that indicates that you do not have permission to access the website, platform, or tool in question. The server successfully receives the quest but denies it for various reasons.
ZeroBounce introduced a new set of WAF rules to enhance its platform security measures in June 2023. These rules meticulously examine all incoming API requests based on a predefined schema that aligns with the ZeroBounce API usage guidelines.
Consequently, if your API request does not adhere to this schema, you will be blocked by the WAF, which results in a 403 Forbidden error.
If you encounter a 403 error, it's recommended to investigate the syntax used for your email service API requests. With the new WAF rules, even minor errors previously tolerated by the API endpoints may now be rejected as non-compliant.
Common examples of such API syntax errors include the following:
To avoid encountering the 403 Forbidden error, carefully review your API requests and verify that they conform to the ZeroBounce API's specified syntax guidelines.
If you've ensured that your API requests meet the new WAF guidelines and are still experiencing a 403 error, don't hesitate to contact ZeroBounce support.
You can contact ZeroBounce via email at support@zerobounce.net or reach out via live chat - available 24/7. The team can help investigate your requests as well as other potential causes for your 403 error. ZeroBounce support is always there to ensure a seamless API integration experience for you.
