Managing Pipedrive API Limits for Clay Lead Retrieval

·

Hello, I’m using the Pipedrive API to check my leads in Clay. However, when there are more than 100 records, I get errors. It seems Pipedrive can’t handle simultaneous API requests like this, and I’m not sure how Clay is sending them. Is there a queue or a way to delay each request? Right now, I have to manually click through each one with a delay, which isn’t ideal.

3 comments

Clay
APP
·
·
Yes, you can set rate limits for your Pipedrive API requests in Clay. In the HTTP API settings, use the "Define rate limit" section to control request frequency: 1. Set a "Request Limit" for the maximum number of allowed requests 2. Define "Duration (in ms)" for the time window (e.g., 1000ms = 1 second) This prevents exceeding Pipedrive's API rate limits by spacing out your requests appropriately.
Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Slava
·
·
Yes, I see “Request Limit”, but how I can set up delay AFTER each request to make sure they’re not being sent at the same time?
Clay
APP
·
·
You can set up rate limiting for your Pipedrive API requests in Clay's HTTP API settings. In the "Define rate limit" section: 1. Set a "Request Limit" (number of allowed requests) 2. Define "Duration (in ms)" (time window in milliseconds) For example, to add delay between requests, you could set a limit of 1 request per 1000ms (1 second).
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University