Hello,
We’re sorry to hear that you’re experiencing the “API Error: HTTP 400” issue on your website. This error typically occurs when the server is unable to process your API request for some reason.
Based on the information provided in our knowledgebase article here, there are several potential reasons for this error, including website maintenance, website status, API timeout, API requests being blocked by a firewall, or having a locally hosted website.
To resolve this issue, we recommend checking the status of your website, ensuring that it is not under maintenance, and verifying that API requests are not being blocked by a firewall. If you are still facing issues after following these steps, please feel free to reach out to our support team directly from here, and we’d be happy to assist you further.
Thank you for bringing this to our attention, and we appreciate your patience as we work to resolve this issue for you.
Sources:
Why Am I Getting “API Error: HTTP 400” Error » Rank Math
How to Fix 429 Error with IndexNow API » Rank Math
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello, I have already tried all the options proposed to solve this error and it is not possible that the error “API Error: HTTP 400 error” stops appearing.
What is the solution?
Hello,
Can you please also confirm if you have whitelisted our IP and user agent as mentioned from the guide as well? https://rankmath.com/kb/api-http-400-error/#blocked-by-firewall
We tested your website in our external SEO Analyzer tool and we see that your site might still be blocking our crawler.
You may also consult your hosting provider.
If that doesn’t help and the issue persists, please let us know here and we will investigate the issue further.
cloudfare TLS 1.2 do it and your problem will be solved.You should set the country barrier as country equals.Field
Country….equals…Tor
Hello @serobaho,
Yes, we are aware of the situation with TLS not working with v1.3 as the SEO Analyzer tool currently only supports up to TLS v1.2, at the moment. The latest version, TLS v1.3, is not yet widely adopted by most websites, so we haven’t updated our tool to work with it. However, we’re planning to do so in the future
@sandralopez1, If you’re using TLS 1.3, we kindly ask you to switch back to TLS 1.2 and see if that solves the problem.
Thank you for your patience and cooperation.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
