Rate Limiting
Rate limiting restricts how many API requests a client can make within a time window. It protects servers from overload and ensures fair access for all users.
Understanding the Concept
Without rate limits, one aggressive client could hammer an API and degrade service for everyone. Rate limiting prevents this by setting boundaries: maybe 100 requests per minute, or 1000 per hour.
For developers, rate limits mean you need to think about efficiency. Batch requests when possible. Cache responses you'll reuse. Handle 429 (Too Many Requests) errors gracefully with exponential backoff.
Good APIs tell you your rate limit status in response headers: how many requests remain, when the limit resets. Use this information to avoid hitting limits in the first place.
Real-World Example
Your trading bot makes 150 requests/minute but the API allows 100. You start getting 429 errors. Solution: batch your price checks into one request for multiple assets, cache reference data, and implement request queuing.
How PRISM Handles This
PRISM uses tiered rate limits based on your plan. Free tier: 60 requests/minute. Developer: 300/minute. Pro: 1000/minute. Enterprise: custom. We return X-RateLimit headers with every response so you always know where you stand.
View API Docs