Rate Limits

These are application-level rate limits for the o2 API. Infrastructure providers may enforce additional network-level limits.

Limiter Types

Type	How it is applied	Used by
IP-based	Based on public IP address	Public or unauthenticated endpoints
Owner ID-based	Based on the O2-Owner-Id header	Session and owner-authenticated endpoints

Session Endpoints

Endpoint	Rate Limit	Type
PUT /v1/session	5/s	Owner ID-based
POST /v1/session/actions	5/s	Owner ID-based

Account Endpoints

Endpoint	Rate Limit	Type
POST /v1/accounts	1/s	IP-based
POST /v1/accounts/actions	10/m	Owner ID-based
POST /v1/accounts/upgrade	10/m	Owner ID-based
POST /v1/accounts/withdraw	10/m	Owner ID-based

Market Endpoints

Endpoint	Rate Limit	Type
GET /v1/markets/fees	5/s	IP-based

Aggregated Endpoints

Endpoint	Rate Limit	Type
GET /v1/aggregated/assets	5/s	IP-based
GET /v1/aggregated/orderbook	5/s	IP-based
GET /v1/aggregated/summary	5/s	IP-based
GET /v1/aggregated/ticker	5/s	IP-based
GET /v1/aggregated/trades	5/s	IP-based
GET /v1/aggregated/coingecko/tickers	5/s	IP-based
GET /v1/aggregated/coingecko/orderbook	5/s	IP-based

All aggregated endpoints are also available under the /v1/agg/ alias with the same rate limits.

Page Size Limits

Some endpoints also cap result size per request:

Data	Limit
Trades	50 items
Orders	200 items
Bars (OHLCV)	5000 bars
Aggregated order book depth	500 levels per side

For cursor behavior, see Pagination.

Client Guidance

• Use WebSocket streams for real-time market and account updates instead of polling aggressively.
• Back off when a request is throttled.
• Include the correct O2-Owner-Id header on owner/session endpoints so owner-based limits apply correctly.
• Batch session actions where appropriate; POST /v1/session/actions supports up to 5 actions total across up to 5 markets.