Overview
The Inbox API enforces rate limits to ensure fair usage and platform stability. This guide covers the limits, how to detect them, and strategies for handling them gracefully.Current limits
Rate limits are global per team — all endpoints share the same limits, and all API tokens for a team share the same quota.
All three windows are enforced simultaneously using a sliding window. If any window is exceeded, requests are rejected until that window resets.
Limits are per team, not per token. Multiple API tokens for the same team share the same rate limit quota.
Rate limit headers
Every response includes rate limit information:Rate limit responses
When you exceed the limit: Status: 429 Too Many RequestsExponential backoff
The recommended pattern for handling rate limits:Bulk operations
For operations that process many items, implement rate-aware batching:Proactive rate limit tracking
Track your usage to avoid hitting limits:Pagination with rate limits
When paginating through large datasets:Best practices
Cache responses
Cache responses
Cache read results to avoid repeated requests:
Monitor rate limit headers
Monitor rate limit headers
Track
X-RateLimit-Remaining and pause before hitting zero.Implement circuit breakers
Implement circuit breakers
Stop making requests temporarily when consistently hitting limits.
Platform considerations
Related
Error codes
All error types including rate limits
Pagination
Efficient data fetching
Working with messages
Send and receive messages
Troubleshooting
Common issues and fixes