Rate Limit Types
Per-Organization Limits
Rate limits are applied at the organization level, shared across all API keys for that organization.Per-Endpoint Limits
Some endpoints have specific rate limits based on their resource intensity:Rate Limit Headers
Every API response includes rate limit information in the headers:Rate Limit Exceeded Response
When you exceed the rate limit, the API returns a429 Too Many Requests response:
Retry-After Header
TheRetry-After header indicates when you can retry:
- Numeric value: Seconds to wait before retrying
- HTTP date: Timestamp when you can retry
Handling Rate Limits
Basic Retry Logic
Proactive Rate Limit Tracking
Request Queue with Rate Limiting
Burst Limits
In addition to per-minute limits, Fanfare implements burst limits to prevent sudden spikes:
Exceeding burst limits returns the same
429 response.
Best Practices
1. Implement Exponential Backoff
2. Use Batch Endpoints
Instead of making individual requests, use batch endpoints where available:3. Cache Responses
Cache read responses to reduce API calls:4. Monitor Rate Limit Usage
Track your rate limit consumption to identify patterns:5. Distribute Load Over Time
For bulk operations, spread requests over time:Plan-Based Limits
Rate limits may vary by subscription plan:
Contact sales for Enterprise rate limit customization.
Rate Limit Exemptions
Certain endpoints are exempt from standard rate limits:- Health check endpoints (
/health) - OpenAPI documentation endpoints (
/openapi.json) - Webhook delivery (outbound)
Monitoring and Alerts
Use the Fanfare dashboard to:- View real-time rate limit usage
- Set up alerts for approaching limits
- Analyze historical usage patterns
Need Higher Limits?
If your use case requires higher rate limits:- Review if batch endpoints can reduce request volume
- Implement caching for read operations
- Contact support for Enterprise plan options