@Nymesia Could excessive calls from your server have resulted in your IP address being temporarily blocked from making further API requests?
To prevent this issue, I recommend implementing rate limiting in accordance with the guidelines outlined here:
https://developers.klaviyo.com/en/docs/rate_limits_and_error_handling#rate-limits
In the meantime contact support as outlined here to get yourself unblocked.
@whereisjad The thing is we already have rate limiting in place that respects the limits per the documentation, so I would have thought it would be enough. But thanks for the support link!
Hi @Nymesia !
I can see that your team has submitted a support ticket - which is what I was going to suggest so they could take a deeper look at this!
If you are provided a solution, please don’t hesitate to share that here so others that experience this in the future can reference this post! :)
Ok, so we found the problem!
Our request server is on Azure and we use a reverse proxy as our rate limiting system. The request between Azure and our rate limiting system contains the header X-Original-URL, which is violating this CVE (this bit of information was given to us by Klaviyo’s support team). This header was also transferred to our request to Klaviyo’s API. However, Klaviyo’s API Cloudflare layer blocks calls which contains the header X-Original-URL, so all our calls were blocked.
To solve the problem, we removed this header in our request to Klaviyo’s API and it looks like it’s working!