Elyse,
Speaking for myself - I’ve already carefully engineered my integrations to meet the currently published API rate limits:
In these docs, it does clearly state that the error we will receive for running afoul of the rate limit will be a ‘429’ http status code.
Is there a new rate limit? It seems your Cloudflare implementation should be aware of your current terms of service to allow for your existing rate limits AND documented error/return codes.
Otherwise, a rate of ‘too high’, is not something I can write a software specification to. I’m looking for a concrete answer to this issue, thanks!