Default Limits
Most endpoints apply the following default rate limit:
Staff-only endpoints (such as character approval and review workflows) apply a stricter limit:
Rate limits are applied per IP address. All requests originating from the same IP — regardless of which user account is authenticated — share the same quota for a given endpoint.
Rate Limit Exceeded Response
When you exceed the allowed number of requests within a window, the API returns an HTTP429 response with the following body:
Retry-After headers, so you should implement your own backoff strategy (see Best Practices below).
Roles That Bypass Rate Limits
Accounts with any of the following roles are exempt from rate limiting and will never receive a429 response:
If your application requires sustained high-volume access, contact the CA Colombia team about obtaining a
BOT role for your integration account.Best Practices
- Cache responses that are unlikely to change frequently (such as user profile data) to reduce the number of requests you make within each window.
- Monitor
429responses in your logging and alerting pipelines so you can identify when a part of your integration is approaching its limit before users are impacted.
