Settings & Configuration
Rate limiting and API quotas
3 minutes read time Difficulty: intermediate
Rate limiting and API quotas
AIsoule enforces rate limits to protect the platform and ensure fair usage.
Login rate limits
| Action | Limit | Window |
|---|---|---|
| Login attempts | 5 | Per minute |
| Registration | 5 | Per minute |
| Token refresh | 30 | Per minute |
| Password reset | 3 | Per hour |
Exceeding these limits temporarily blocks the action.
API rate limits
| Limit | Value |
|---|---|
| Requests per minute | 100-200 (plan dependent) |
| Burst (per second) | 10 |
| Request body size | 5 MB |
Messaging limits (Meta)
These are enforced by Meta, not AIsoule:
- Tier-based unique contacts per day (250 → 1K → 10K → 100K)
- Template submissions: 100 per hour
- Media uploads: 500 per day
What happens when limited
- API calls → HTTP 429 response with retry-after header
- Login → "Too many attempts" error, wait 60 seconds
- Messaging → Messages queued or failed with rate limit error
Tips
- Implement retry logic — For API integrations
- Spread requests — Don't burst all at once
- Cache data — Reduce unnecessary API calls
- Monitor usage — Check rate limit headers in responses
- Contact support — If you need higher limits for your use case
Related Articles
Was this guide helpful?
Your feedback helps us make these guides better for everyone.