Rate limits

To ensure system stability and protect against overloading, our API enforces rate limits. If these limits are exceeded, the API will return an HTTP status code 429 - Too Many Requests.

Rate-limited Actions

The following actions are subject to rate limiting:

• Simultaneous connections from the same IP address.
• Simultaneous connections from the same API account.
• Requests per second from the same IP address.
• Requests per second from the same API account.
• New connections per second from the same IP address.

Best practices

To avoid reaching the rate limits and to maximize performance:

• Minimize simultaneous connections: Typically, using more than a few concurrent connections will not significantly improve performance.
• Use persistent connections: Reuse existing connections for consecutive API requests to reduce overhead and improve efficiency.

Default rate limits (as of 2024-02-29)

• Requests per second: The default limit is 200 requests per second, with allowance for bursts of up to 500 requests per second.
• Simultaneous connections: The default maximum is 64 concurrent connections.

Need higher limits?

If your application requires higher rate limits, please contact us to discuss increasing your allocated resources.