Deel enforces rate limits to ensure API stability and fair usage across all integrations. Understanding and respecting these limits is essential for building reliable applications.
Rate limits are enforced per organization, not per token. All API tokens within your organization share the same rate limit quota. If you have multiple services or processes making API calls, they all count toward the same 5 requests/second limit.
The rate limit operates on a rolling 1-second window:
When you exceed 5 requests per second:
429 status codeDeel API does not return rate limit headers. You won’t know you’ve hit the rate limit until you receive a 429 error. This makes proactive rate limiting especially important.
When you exceed the rate limit, you’ll receive a 429 error:
Implement exponential backoff when hitting rate limits:
Queue requests to ensure you never exceed 5 requests per second:
When possible, use batch operations instead of individual requests:
Avoid bursts of requests. Spread them out over time:
Reduce API calls by caching frequently accessed data:
Since rate limits are organization-wide, centralize request handling to avoid conflicts:
Important: Since rate limits are per organization, using multiple tokens won’t increase your rate limit. Instead, coordinate all API requests through a centralized queue.
✅ Always implement request queuing
✅ Use exponential backoff for 429 retries
✅ Cache frequently accessed data
✅ Space out requests (avoid bursts)
✅ Set up alerts for rate limit errors
✅ Monitor 429 error frequency
✅ Centralize API requests across your organization
❌ Don’t send bursts of requests
❌ Don’t ignore 429 errors
❌ Don’t retry immediately without delay
❌ Don’t make unnecessary API calls
❌ Don’t use tight polling loops
❌ Don’t assume you know remaining quota (no headers provided)
❌ Don’t run multiple uncoordinated processes making API calls
Solutions:
Possible causes:
Solutions:
Immediate actions: