Rate Limits
HookWatch implements rate limits to ensure fair usage and platform stability. This page explains the different limits and how to work within them.
API Rate Limits
Rate limits apply to REST API requests. Limits are per-user and reset every minute.
| Plan | Requests/Minute | Burst Limit |
|---|---|---|
| Free | 60 | 10 |
| Pro | 300 | 50 |
| Business | 1000 | 100 |
Plan Quotas
These limits define what you can create and how much you can use per month.
| Resource | Free | Pro | Business |
|---|---|---|---|
| Endpoints | 3 | 25 | Unlimited |
| Events/Month | 10,000 | 100,000 | 1,000,000 |
| Cron Jobs | 5 | 50 | Unlimited |
| Event Retention | 7 days | 30 days | 90 days |
| API Keys | 2 | 10 | 50 |
Rate Limit Headers
Every API response includes headers to help you track your rate limit status:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed per minute |
X-RateLimit-Remaining | Requests remaining in current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Retry-After | Seconds to wait before retrying (only on 429) |
Handling Rate Limits
1. Monitor Headers
Check X-RateLimit-Remaining to know when you're approaching
the limit. Slow down before hitting 0.
2. Implement Exponential Backoff
When you receive a 429 response, wait for the time in Retry-After, then retry. If it fails again, double the wait time.
3. Batch Requests
Where possible, use bulk endpoints instead of making many individual requests.
4. Cache Responses
Cache responses for data that doesn't change frequently to reduce API calls.
Webhook Delivery Limits
These limits apply to incoming webhook delivery, not API requests.
| Limit | Value |
|---|---|
| Max request body size | 1 MB |
| Request timeout | 30 seconds |
| Delivery timeout | 30 seconds |
| Concurrent deliveries per endpoint | 10 |
Need Higher Limits?
If you need higher rate limits or quotas, upgrade your plan or contact us for enterprise options.