Usage limit overview
API call limits per month depend on your plan.How API blocking works
When a Free or Trial account exceeds its monthly API call limit, the API returns a429 Too Many Requests response:
Response headers
Blocked responses may include aRetry-After header indicating seconds until the monthly reset.
Handling rate limits
Detecting rate limits
Check for HTTP status code429:
What to do when blocked
- Check your usage in Settings → Billing
- Reduce call volume with caching and webhooks
- Wait for the monthly reset or upgrade your plan
Paid plans are not blocked for monthly API call overages. If you see
429 on a paid plan, contact support.Best practices for avoiding rate limits
1. Always include trailing slashes
All ButterCMS API URLs require a trailing slash. Requests without a trailing slash receive a301 Redirect to the correct URL, which causes your client to make a second request — doubling your API call count.
2. Batch related requests
Instead of making many small requests, use features like: Multi-collection retrieval:3. Implement client-side caching
Cache API responses in your application:4. Use webhooks for real-time updates
Instead of polling the API for changes, use webhooks to receive notifications when content changes:- Reduces unnecessary API calls
- Provides immediate update notifications
- More efficient for cache invalidation
Write operations
Write API calls count toward your monthly API usage. For large imports, pace requests and monitor usage to avoid hitting monthly limits on Free or Trial accounts.Monitoring API usage
Track your requests
Implement logging to understand your API usage patterns:Check ButterCMS status
Monitor the ButterCMS Status Page for:- Service availability
- Planned maintenance
When you need higher monthly limits
If your application requires higher monthly API call limits:- Review your implementation - Often, optimizations can reduce API calls significantly
- Contact ButterCMS support - Discuss your use case at support@buttercms.com
- Consider plan upgrades - Higher-tier plans include increased limits
Summary
| Best Practice | Impact |
|---|---|
| Always use trailing slashes | Prevents redirect doubling your call count |
| Batch collection requests | Fetches multiple collections in one call |
| Implement client caching | Fewer API calls |
| Use webhooks | Eliminates polling |
Respect Retry-After | Clear recovery for 429 blocks |