You can control Clay's request rate by setting up rate limiting in your HTTP API configuration. In the "Define rate limit" section, set your Request Limit to match the API's allowed requests and Duration (in ms) for the time window. [1]
For example, if an API allows 100 requests per minute, set Request Limit to 100 and Duration to 60000 ms. [2] The rate limit must average at least 5 requests per second to work properly.
This prevents Clay from overwhelming slower APIs during bulk operations by throttling requests to stay within their limits. [3]
If you need any more help with adjusting the rate limits for your HTTP API bulk runs, please let me know. Would you like to provide more details about what you're trying to achieve or any specific challenges you're facing?