Rate limiting controls how many requests your account can make in a given time window. It's one of the core ways AliasFleet protects both your account and the platform from abuse — whether that's a script running amok, a bad actor probing the system, or just a browser tab that's refreshing too aggressively.
How it works
Every API request you make — loading your alias list, fetching sessions, creating a destination — counts against your rate limit. Limits are measured per minute, per account.
When you hit the limit, you'll get a 429 Too Many Requests response. Normal usage never comes close to triggering this.
Limits by plan
| Plan | Requests per minute |
|---|---|
| Free | 50 |
| Pro | 100 |
| Business | 200 |
These limits apply to general API usage. Specific sensitive operations have their own separate, stricter limits regardless of plan — see below.
Separate limits for sensitive operations
Some actions have independent rate limits that apply across all plans:
- Login attempts — 5 attempts per 15 minutes per IP. Blocks for 10 minutes after that.
- Password reset requests — 3 per hour.
- Sign-up — 5 accounts per hour per IP.
- Verification email resends — limited to prevent email spam abuse.
These can't be increased by upgrading your plan — they're security floors, not usage quotas.
What happens when you hit a limit
You'll see an error message telling you how long to wait before trying again. The block lifts automatically — there's nothing to do except wait. For general API limits, this is typically under 60 seconds.
If you're hitting limits regularly
Normal day-to-day use of AliasFleet — browsing your aliases, managing destinations, checking activity — won't come close to these limits. If you're regularly hitting them, it's usually caused by:
- A browser extension or automation script making rapid repeated requests
- Rapid tab refreshing during a slow connection
- A custom integration that isn't respecting standard HTTP backoff
If you're building an integration and need higher limits, upgrading to Pro or Business is the right path.
See also: Understanding Your Plan Limits · Too Many Requests Error