The Bags API implements rate limiting to ensure fair usage and system stability.Documentation Index
Fetch the complete documentation index at: https://docs.bags.fm/llms.txt
Use this file to discover all available pages before exploring further.
Rate Limit Overview
- Rate limit: 1,000 requests per hour per user and per ip
- Scope: Rate limits apply across all your API keys
- System: Sliding hourly windows (not fixed periods)
Endpoint-Specific Limits
Certain endpoints may enforce additional, endpoint-specific rate limits. These limits are intentionally not publicly disclosed and apply only to the affected endpoints. Under normal usage patterns you should not encounter these limits. If you do get rate limited, please reach out to us so we can help.Response Headers
Monitor your API usage through response headers included with every request:X-RateLimit-Limit: Total requests allowed per hour (1,000)X-RateLimit-Remaining: Requests remaining in current windowX-RateLimit-Reset: Unix timestamp when the limit resets
Sliding Window System
Rate limits use sliding hourly windows rather than fixed periods:- Window 1: 1:00 PM - 2:00 PM
- Window 2: 2:00 PM - 3:00 PM
- And so on…
Monitoring Usage
Rate Limit Exceeded
When you exceed your rate limit, the API returns a429 status with additional information:
Rate Limit Planning
Calculate Request Budget
Plan your API usage based on your application’s needs:- 1,000 requests/hour = ~16.7 requests/minute = ~0.28 requests/second
- High-frequency apps: Consider request batching or caching
- Background jobs: Spread requests across the hour
