Pipedrive · Rate Limits
Pipedrive Rate Limits
Pipedrive enforces a token-budget rate-limit model. Each company has a daily allocation of base tokens × plan multiplier × number of seats (plus any purchased top-ups). Different operations cost different amounts; per-user burst limits apply in 2-second windows. Resets daily at server midnight.
7 Limits
Throttle: 429
CRMSalesRate LimitingThrottling
Limits
Daily Token Budget company
30,000 base tokens × plan multiplier × number of seats (+ top-ups). Plan multiplier ranges from 1 (Lite) to 7 (Ultimate). Resets daily at server midnight.
Single Entity GET Cost request
2
Retrieving a single entity (e.g. GET /deals/{id}) costs 2 tokens.
List GET Cost request
20
Listing multiple entities (e.g. GET /deals) costs 20 tokens.
Update Cost request
10
PUT / PATCH / POST mutating a single entity costs 10 tokens.
Search Cost request
40
Search endpoints cost 40 tokens per call.
Per User Burst (2 second window) user
Per-user burst restrictions apply in 2-second windows; e.g. Lite users may make ~20 token-equivalent requests per 2-second window.
Webhook Delivery subscription
Webhook deliveries are retried on 5xx; receivers should respond 2xx within the platform timeout.
Policies
Backoff Strategy
Implement exponential backoff with jitter on 429. Daily exhaustion requires waiting until midnight server time or buying a top-up.
Cost-Aware Design
Prefer single-entity GETs when possible; avoid using search when a direct list+filter works. Cache responses and use webhooks instead of polling.
Pagination
Use limit + start cursor on list endpoints to avoid exhausting the list-GET budget.