Rate Limits
ApexApi enforces rate limits to ensure fair usage and service stability. Limits are based on your account tier.
Rate Limit Tiers
Your tier is automatically determined by your total credit purchases. As you spend more, your limits increase.
| Tier | RPM | RPD | Concurrency |
|---|---|---|---|
| Free For testing and development. | 10 RPM | 100 RPD | 2 |
| Starter For personal projects and prototypes. | 60 RPM | 1,000 RPD | 5 |
| Growth For production applications. | 300 RPM | 10,000 RPD | 20 |
| Scale For high-volume applications. | 1,000 RPM | 100,000 RPD | 50 |
| Enterprise Contact us for custom limits. | Custom | Custom | Custom |
RPM = Requests Per Minute. RPD = Requests Per Day.
Rate Limit Headers
Every API response includes rate limit information in the response headers.
X-RateLimit-LimitThe maximum number of requests allowed in the current window.
X-RateLimit-RemainingThe number of requests remaining in the current window.
X-RateLimit-ResetUnix timestamp when the rate limit window resets.
Retry-AfterSeconds to wait before retrying (only present on 429 responses).
Handling Rate Limits
Monitor headers
Check X-RateLimit-Remaining in every response to proactively throttle your requests before hitting the limit.
Exponential backoff
When you receive a 429 response, wait for the duration specified in the Retry-After header. If not present, use exponential backoff starting at 1 second.
Request queuing
For high-volume applications, implement a request queue that respects your concurrency limit and spaces out requests evenly.