This is a guide on Upbit API’s request rate limit policy and its implementation instructions.
General Policy
- Rate limits are primarily applied on a per-second basis.
- APIs in the same Rate Limit Group share the same request quota. You can check the group and applicable policy for each API in the tables below or in the Rate Limit section of each API Reference page.
- The maximum number of allowed requests may change with prior notice. Additional restrictions may also be applied depending on service conditions. Monitor your remaining request quota and avoid sending excessive requests.
- Requests that include an
Originheader are subject to a separate policy. For both Quotation REST API and WebSocket requests, only 1 request per 10 seconds is allowed. See the related announcement for details. - Private WebSocket(
/websocket/v1/private)is subject to a concurrent connection limit per Account, separate from the request rate limits. For more details, refer to the WebSocket Usage and Error Guide.
REST API Rate Limits
Requests are limited by Rate Limit Group. APIs that belong to the same group share the same quota.
Quotation REST API
| Rate Limit Group | Request Limit | Measurement Unit | Target APIs |
|---|---|---|---|
market | Up to 10 requests per second | IP | List Trading Pairs |
candle | Up to 10 requests per second | IP | List Second Candles List Minute Candles List Day Candles List Week Candles List Month Candles List Year Candles |
trade | Up to 10 requests per second | IP | List Pair Trades |
ticker | Up to 10 requests per second | IP | List Tickers by Pairs List Tickers by Market |
orderbook | Up to 10 requests per second | IP | Get Orderbook List Orderbook Instruments |
Exchange REST API
Travel Rule Verification Request LimitTravel Rule verification using a deposit UUID or TxID can be requested at most once every 10 minutes for the same deposit.
WebSocket Rate Limits
- WebSocket connection requests (handshakes) are limited to a maximum of 5 requests per second. The limit is applied per IP address for unauthenticated connections and per Pocket for authenticated connections.
- After a connection is established, data request messages are limited to a maximum of 5 requests per second and 100 requests per minute per connection.
- If the rate limit is exceeded, connection requests are rejected with
HTTP 429 Too Many Requestswhile data request messages result in aTOO_MANY_REQUESTerror response followed by connection termination. For more details, refer to the WebSocket Usage and Error Guide documentation. - Private WebSocket(
/websocket/v1/private)is subject to a concurrent connection limit per Account (maximum of 5 connections per Endpoint), separate from the request rate limits. For more details, refer to the WebSocket Usage and Error Guide. - We recommend maintaining and reusing existing connections rather than repeatedly connecting and disconnecting.
How to Check Your Remaining Request Quota
The remaining request quota is returned in the Remaining-Req header of REST API responses.
Remaining-Req: group=default; min=1800; sec=29| Field | Description |
|---|---|
group | The Rate Limit Group that the request belongs to. |
min | Deprecated — A legacy per-minute field. This field is no longer used. We recommend that you do not reference it when processing responses. |
sec | The number of requests remaining in the current second. If the value is 0, wait before sending additional requests. |