User's UI actions are counted in the rate limit. Demanding actions such as data import might also take a relevant amount of the allowed requests for a limited time frame. Webhooks are not subjected to rate limiting.
Rate limiting of the Pipedrive API is considered per access_token or api_token. All our API endpoints require authentication. Regardless of the authentication method, the Pipedrive API allows performing requests according to the plan.
The Pipedrive API rate limit window duration is 2 seconds. Each of our three plans offers different rate limiting per 2-second window:
Silver
20 requests per 2 seconds per access_token or api_token
Gold
40 requests per 2 seconds per access_token or api_token
Platinum
80 requests per 2 seconds per access_token or api_token
Each Pipedrive API request will include the following rate limit response headers:
x-ratelimit-limit
The maximum number of requests current access_token or api_token can perform per 2-second window.
x-ratelimit-remaining
The number of requests left for the 2-second window.
x-ratelimit-reset
The remaining window before the rate limit resets.
For example, after a successful request has been made from a Gold plan account, the API response headers would look like this:
x-ratelimit-limit: 40
x-ratelimit-remaining: 39
x-ratelimit-reset: 2
If you exceed the rate limit, our API will start rejecting your requests and you'll receive an error response of HTTP 429 "Too Many Requests" in the body:
{"success":false,"error":"request over limit","errorCode":429}If you're reaching the rate limit, options to improve performance include restructuring the architecture of the integration, using Webhooks, and/or upgrading to Gold or Platinum plan.
Further reading
| Responses |