Rate Limits
The Wappfy API enforces rate limits to ensure fair usage and platform stability.Default limits
| Scope | Limit | Window |
|---|---|---|
| Per user | 100 requests | 1 minute |
| Per IP (unauthenticated) | 20 requests | 1 minute |
Rate limit headers
Every response includes rate limit information:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the window |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Handling rate limits
When you exceed the limit, you’ll receive a429 response:
Best practices
Implement exponential backoff
Implement exponential backoff
When you receive a 429, wait and retry with increasing delays: 1s, 2s, 4s, 8s…
Use the Reset header
Use the Reset header
Check
X-RateLimit-Reset to know exactly when you can resume.Batch operations where possible
Batch operations where possible
Send messages with reasonable delays between them rather than bursting.
Cache responses
Cache responses
Avoid re-fetching data that hasn’t changed (e.g., instance details, contact info).