Temporary Rate Limits and How Jotform Decides Which Requests to Block

Hey Lara,

One of our customers reached out to Jotform and was informed that, at times, Jotform imposes temporary rate limits based on traffic patterns and system load. They mentioned that even if an account is within its daily rate limit, it could still encounter these errors.

Could you possibly explain a bit more about how these temporary rate limits are imposed? For example, is it a specific IP address that gets blocked, or how exactly is this determined? I'm asking because, on our end, only a handful of integrations get blocked—not all of them—so I’m trying to understand how Jotform decides which requests to deny.

I’m bringing this up here because I’d prefer it if our customer doesn’t have to engage in a technical discussion with Jotform support, as they are not very technical themselves.

Hi Jalal,

Regarding your question about temporary rate limits, Jotform may apply these limits based on things like traffic patterns and system load. So, even if an account is within its daily limit, it might still run into errors if the system detects high traffic or unusual activity. The system monitors overall API usage to make sure everyone gets fair access.

Let us know if you have any other questions.