How to Fix the Rate Limit Too Low Issue When Setting Limits

Siddanth S. · 2026-02-05T15:51:14.914Z

I'm trying to set the rate limit for but I'm getting a issue saying rate limit too low. Is there a workaround to this?

How to Fix the Rate Limit Too Low Issue When Setting Limits | Clay

11 comments

· Sorted by Oldest

Clay Support
APP
·
·
The "rate limit too low" error happens because your current settings don't meet the minimum requirement. The rate limit must average at least 5 requests per second to work properly.
Your current setup (600 requests per 3,600,000 ms) equals about 0.17 requests per second, which is way below the 5 requests/second minimum.
To fix this, you need to increase your request limit or decrease the duration. For example:
600 requests per 120,000 ms (2 minutes) = 5 requests/second
Or 18,000 requests per 3,600,000 ms (1 hour) = 5 requests/second
Just make sure your final calculation gives you at least 5 requests per second.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help adjusting your rate limit settings, I’m here to assist. Would you like to provide more details about what you’re trying to achieve with the rate limit?
Siddanth S.
·
·
can I speak to human?
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Ashwin D.
·
·
Hey Siddanth - thank you for reaching out. Unfortunately, there is a minimum rate limit set so that the table doesn't run for a prolonged period of time. What workflow are you trying to make?
Siddanth S.
·
·
this is Lusha's API and their rate limit is super low
Siddanth S.
·
·
we are using it to find emails
Ashwin D.
·
·
Our current minimum is 1 request per second. One workaround could be setting up Postman as a middle man for this. Potential Postman Setup:
Receives requests from Clay at Clay's rate (1+ req/sec)
Queues and throttles those requests to match your API's lower limits
Forwards them to your actual API at the slower rate
Returns responses back to Clay
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!

Clay Support
APP
·
·
The "rate limit too low" error happens because your current settings don't meet the minimum requirement. The rate limit must average at least 5 requests per second to work properly.
Your current setup (600 requests per 3,600,000 ms) equals about 0.17 requests per second, which is way below the 5 requests/second minimum.
To fix this, you need to increase your request limit or decrease the duration. For example:
600 requests per 120,000 ms (2 minutes) = 5 requests/second
Or 18,000 requests per 3,600,000 ms (1 hour) = 5 requests/second
Just make sure your final calculation gives you at least 5 requests per second.
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need help adjusting your rate limit settings, I’m here to assist. Would you like to provide more details about what you’re trying to achieve with the rate limit?
Siddanth S.
·
·
can I speak to human?
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon!
If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Ashwin D.
·
·
Hey Siddanth - thank you for reaching out. Unfortunately, there is a minimum rate limit set so that the table doesn't run for a prolonged period of time. What workflow are you trying to make?
Siddanth S.
·
·
this is Lusha's API and their rate limit is super low
Siddanth S.
·
·
we are using it to find emails
Ashwin D.
·
·
Our current minimum is 1 request per second. One workaround could be setting up Postman as a middle man for this. Potential Postman Setup:
Receives requests from Clay at Clay's rate (1+ req/sec)
Queues and throttles those requests to match your API's lower limits
Forwards them to your actual API at the slower rate
Returns responses back to Clay
Clay Support
APP
·
·
We haven't heard back from you here, so we're going to go ahead and close this thread out.

Still need help here? Reply back and someone will jump back in.

Have a question thats not related to this thread? We recommend kicking off a new ticket in the support channel!