Troubleshooting Perplexity AI API 429 Rate Limit Errors

Lemuel C. · 2025-01-20 20:19:43.290988+00

I am using HTTP API with Perplexity AI endpoint. Perplexity has a 50 request per minute. In the clay HTTP API, we can set Custom Rate Limit. I tried different combinations but no avail... I am still getting 429 error "request rate limit exceeded"

Troubleshooting Perplexity AI API 429 Rate Limit Errors | Clay

8 comments

· Sorted by Oldest

Channeled
APP
·
·
To configure the Custom Rate Limit for the Perplexity AI endpoint in Clay's HTTP API: 1. Locate the "Define rate limit" section in your HTTP API integration settings 2. Set the following values: • Request Limit: 50 (to match Perplexity's limit) • Duration: 60000 (milliseconds, which equals 1 minute)This configuration will ensure Clay respects Perplexity's rate limit of 50 requests per minute, helping you avoid the 429 error. Source: HTTP API with JWT authentication | Documentation | Clay University
Lemuel C.
·
·
Already tried 50 with 60000 but a prompt error message "Rate Limit too low"
Channeled
APP
·
·
Based on the error message you're receiving, it seems the rate limit settings you're trying to use are too restrictive for Clay's system. While the HTTP API integration allows you to set custom rate limits, you'll need to try a higher request limit or shorter duration to resolve this error.Here's what you can try: ** Increase the Request Limit above 50 ** Decrease the Duration (in ms) to something lower than 60000 * Test different combinations (e.g., 100 requests per 60000ms or 50 requests per 30000ms)The rate limit settings help prevent exceeding API rate limits while ensuring smooth operation within Clay's system. As a reference point, for other API integrations like Kitt AI, the recommended custom rate limits are typically 5 requests per 1000ms. Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University Verify Email with Kitt AI | Clay.com
Channeled
APP
·
·
Hi Lemuel C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Mark L.
·
·
Hi Lemuel, in the rate limits section the (i) info tooltips clarify: for Clay, the limit must be at least 5 per second. This comes up every so often, and to my knowledge, there are no immediate plans to change it. One reason why is that we don't want e.g. tables to run for days if there were a large volume of rows. We do have a native integration with Perplexity. I'm curious if that will meet your needs or if you've already discarded that option.
🥲1
Channeled
APP
·
·
Hi Lemuel C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
To configure the Custom Rate Limit for the Perplexity AI endpoint in Clay's HTTP API: 1. Locate the "Define rate limit" section in your HTTP API integration settings 2. Set the following values: • Request Limit: 50 (to match Perplexity's limit) • Duration: 60000 (milliseconds, which equals 1 minute)This configuration will ensure Clay respects Perplexity's rate limit of 50 requests per minute, helping you avoid the 429 error. Source: HTTP API with JWT authentication | Documentation | Clay University
Lemuel C.
·
·
Already tried 50 with 60000 but a prompt error message "Rate Limit too low"
Channeled
APP
·
·
Based on the error message you're receiving, it seems the rate limit settings you're trying to use are too restrictive for Clay's system. While the HTTP API integration allows you to set custom rate limits, you'll need to try a higher request limit or shorter duration to resolve this error.Here's what you can try: ** Increase the Request Limit above 50 ** Decrease the Duration (in ms) to something lower than 60000 * Test different combinations (e.g., 100 requests per 60000ms or 50 requests per 30000ms)The rate limit settings help prevent exceeding API rate limits while ensuring smooth operation within Clay's system. As a reference point, for other API integrations like Kitt AI, the recommended custom rate limits are typically 5 requests per 1000ms. Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University Verify Email with Kitt AI | Clay.com
Channeled
APP
·
·
Hi Lemuel C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Mark L.
·
·
Hi Lemuel, in the rate limits section the (i) info tooltips clarify: for Clay, the limit must be at least 5 per second. This comes up every so often, and to my knowledge, there are no immediate plans to change it. One reason why is that we don't want e.g. tables to run for days if there were a large volume of rows. We do have a native integration with Perplexity. I'm curious if that will meet your needs or if you've already discarded that option.
🥲1
Channeled
APP
·
·
Hi Lemuel C.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: