Every AliasFleet plan includes a per-minute API limit — the number of requests your account can make in any 60-second window. For most users this is invisible. It matters most if you're building an integration, using the browser extension heavily, or have multiple tabs open simultaneously.
Limits by plan
| Plan | Requests per minute |
|---|---|
| Free | 50 |
| Pro | 100 |
| Business | 200 |
Limits apply per account, not per device. If you have three tabs open, their requests all count toward the same limit.
What counts as a request
Almost any interaction that fetches or changes data counts:
- Loading your alias list or a single alias
- Creating, updating, or deleting an alias
- Fetching activity logs
- Loading destinations or creating a new one
- Viewing active sessions
- Checking billing or usage data
Static page loads (navigating between pages) are fast and don't hammer the limit. Normal browsing won't come close to 50 requests per minute.
What doesn't count
Email forwarding itself is server-side infrastructure and is completely unaffected by rate limits. Your aliases will keep forwarding regardless of API limit status.
Separate security limits
Some sensitive operations have their own independent limits that apply across all plans, regardless of your API allowance:
| Operation | Limit |
|---|---|
| Login attempts | 5 per 15 minutes (per IP) |
| Password reset requests | 3 per hour |
| Sign-up | 5 per hour (per IP) |
| Verification email resends | Limited per destination |
These can't be increased by upgrading — they're security floors.
When you hit the limit
You'll see a "Too many requests" error with a wait time. The block clears automatically — usually within 60 seconds. See Too Many Requests Error for more detail.
Upgrading for higher limits
If you're building an integration or regularly hitting limits, upgrading your plan doubles or quadruples your allowance. Changes take effect immediately after upgrading.