Managing Rate Limits in Clay: Workarounds and Solutions

·

Hi there, I keep getting rate limited in Clay. Ive set the minimum rate to 5 req/second, but the api im using is less then that and I keep having to manually re-reunning the column.. "run all rows that havent run or have errors" Obviously this is sustainable. Any work around?

2 comments

Channeled
APP
·
·
The rate limit in Clay must average at least 5 requests per second to work properly. To prevent rate limiting: 1. Check your "Request Limit" and "Duration (in ms)" settings in the HTTP API configuration. 2. Ensure your duration setting is appropriate - remember that 1000 ms equals 1 second. 3. Try processing data in smaller batches (e.g., 200 rows at a time) to stay within rate limits. For rows with errors, you'll need to manually rerun them using the "run all rows that haven't run or have errors" option as there's no automatic rerun feature currently available.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University Apollo.io integration overview | Documentation | Clay University
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.