Request Rate Limit

The limit on the number of EXCHANGE API and QUOTATION API requests for accurate confirmation on the request condition is listed below.

Date : 2020-03-03
Updated : 2023-10-24

Updated about change of Request Limit Policy ('Account-based' Limit, no limit on requests 'per minute')
The followings are the additional notes on the standards for the limit on the number of requests besides orders.
Also the total of the available key issuing per account.

Common Notes

An IP address is required when issuing an Open API Key and 5 IP addresses per key is allowed as the maximum.
Issue 10 Open API keys per account.
The request rate limit is counted by each API key.
Must select needed functions and IP address when issuing an API key. Manage and issue API keys through this page. Kindly refer to the API key list request to request the key list using Open API.

EXCHANGE API

[Order Request]

8 times/sec

[Other API Request]

30 times/sec
- 1 Request for the same deposit transaction once every 10 minutes for Travel Rule Verification API. For more information click here.

[Additional notes on Exchange API]

(Update) Request rate limit is measured on an account basis.
Even in the case of requests within this standard, if multiple Open API Keys are used on one account, the number of requests may be limited to provide stable service for the entire Upbit.
The above number of requests may not be temporarily guaranteed depending on the conditions for the server and services.
Check the remaining number of available requests by referring to the method below which describes how to check the remaining number of requests.
(Update) The order request API and non-order request API request limit are counted separately.

QUOTATION API

Limit the number of Websocket connection requests
1. Upon requesting a WebSocket connection with authentication information (jwt token) in the header it is measured on an account basis. (*To receive Public data, no special authentication is required, but authentication is required to receive Private data.)
  - WebSocket connection request: 5 times/sec
  - WebSocket Data Request*: 5 times/sec, 100 times/min
    *Data requested such as My Trade (execution data) upon connection.
2. Upon requesting a WebSocket connection without authentication information, it is measured on an IP basis.
  - WebSocket connection request: 5 times/sec
  - WebSocket Data Request*: 5 times/sec, 100 times/min
    *Data requested such as Current Price/ Execution/ Order Book information for a specific market
REST API limit is measured on an IP basis.

10 times/sec (Market, Candle, Execution, Ticker, Order Book has its own limit)

[Additional notes on Quotation API]

To ensure consistent service in the future, the amount of API requests may be modified. We will notify you through a separate notice to keep you informed
The time condition that applies to the limit on the number of requests is based on the time of the first request and is initiated after a certain period of time. (Failed requests are not included in the number of requests.)
If you need multiple REST API requests, please receive them through WebSocket.

The Upbit Developer Center is committed to providing more stable and advanced services in the future.

If there are any changes to the limit on the number of requests in the future, we will make sure to notify you through a separate notice.

[Check the Remaining Exchange API Requests]

Upbit Open API service puts a limit on the number of requests per second for a seamless usage environment. When you call API, the number of remaining requests can be seen through the Remaining-Req response header.

Remaining-Req: group=default; min=1799; sec=29

If you received a response header in the format above, this means you are allowed to make 29 requests that second and 1,799 requests during the remaining 1 minute for the default group.

🚧
If there are requests that exceed the allotted time, a 429 Too Many Requestserror may occur. However, no additional penalty will be imposed.