Open Platform API rate limits
Purpose
Describes rate limiting by dimension and time window so you can stay within quotas and avoid 60001 responses.
Definitions
Dimensions
| Key | Name | Description |
|---|---|---|
| USER | User | Per caller identity (e.g. user id) |
| APP | Application | Per app tied to the API key |
| GLOBAL | Global | Whole platform ceiling |
Windows
| Key | Unit | Description |
|---|---|---|
| SECOND | Second | 1-second sliding/count window |
| MINUTE | Minute | 60-second window |
Limits
Multi-dimensional; any breached limit fails the request:
| Dimension | Window | Limit | Note |
|---|---|---|---|
| USER | Second | 100/s | Max 100 calls per second per user |
| USER | Minute | 5000/min | Max 5000 calls per minute per user |
| APP | Second | 20/s | Max 20 calls per second per app |
| APP | Minute | 1000/min | Max 1000 calls per minute per app |
| GLOBAL | Second | 3000/s | Platform-wide per second |
| GLOBAL | Minute | 150000/min | Platform-wide per minute |
The strictest applicable limit wins: e.g. 101 calls in one second hits the per-second cap even if the minute quota is unused.
When limited
- HTTP/body: status
60001(INTERFACE_RATE_LIMIT), message similar to Rate limit exceeded, please try again later. - Recovery: wait until the current window rolls over; counters reset.
Notes
- Counts include failed validation/auth attempts that the gateway still processes.
- Implement client-side throttling and split bursts to avoid spikes.
- Higher quotas may be arranged with platform operations.
- Limits may change; watch platform announcements.