Feeds / Crypto exchanges (live)

Upbit

Spot (USDT market). Every orderbook message is a full 15-level book that replaces the previous one.

Live in productionWebSocket15 levels per side

Live now

-
books live
-
messages / s
-
level changes / s
-
KB / s

Messages / s and KB / s are what our handler receives from the exchange (KB after decompression, REST snapshots included); level changes / s are counted after normalization, for the markets we publish.

Open live books Replay

How we connect

Market
Spot (USDT market)
WebSocket
wss://api.upbit.com/websocket/v1
Channels
orderbook — 15 levels, full book in every message
trade — trades
Update model
Every orderbook message is a full 15-level book that replaces the previous one.
Sequencing
None needed: each message is a complete book.
On a gap
Not applicable. On a socket error, close, or 30 s without data the handler reconnects and re-sends one subscribe listing every symbol.
Depth
15 levels per side
Authentication
none
Heartbeat
Client sends a PING text frame every 60 s; WebSocket pings answered.
Symbol format
USDT-BTC (quote first)

Subscribe message

[{"ticket":"mdf-upbit-batch"},{"type":"orderbook","codes":["USDT-BTC.15","USDT-ETH.15",...]},{"type":"trade","codes":["USDT-BTC",...]},{"format":"SIMPLE"}]

What our handler takes care of

Instruments

loading...

Upcoming and recent changes

2026-11-17Action neededOpen API Terms of Use revision (effective 12/10)effective 2026-12-10
Upbit announced a revision to the Open API Terms of Use that takes effect on 12/10. The page shows only the headline, not the revised terms.
Details

The changelog lists only the headline 'Open API 이용약관 개정 안내 (12/10 적용 예정)' (about 7 days before today). No details of the revised clauses are given. The terms page shown is the version applicable since 2024-10-30. Under the terms, users must review the notice and accept or reject the revision before the effective date. The year is inferred from the context of the current date, not stated.

Our handler: This is a legal terms update, not a change to the websocket orderbook or trade channels, though it governs use of the Open API.

Source ↗

2026-11-17MaintenanceServer maintenance notice (completed)May affect market data
Upbit posted a server maintenance notice that is marked as completed. The page gives no times or scope.
Details

The entry '[중요]서버 점검 안내(완료)' appeared about 12 days ago and is marked complete. The visible text contains no window, affected services or required client action. No action is needed since it has finished.

Our handler: Server maintenance could have interrupted the websocket feed, but the scope is not stated and it is already complete.

Source ↗

2026-11-17Action neededAPI path format and error handling review noticeMay affect market data
Upbit posted an important notice about reviewing API path formats and error handling. The page shows only the headline.
Details

The entry '[중요] API Path 형식 및 오류 처리 방식 점검 안내' appeared about 20 days ago and is tagged Improved. No details or dates are visible. Check the full notice for whether REST path formats or error responses change. Our handler uses only the websocket, so impact is likely limited.

Our handler: Path format and error handling changes mainly concern REST endpoints, but websocket error responses might be affected; details are not shown.

Source ↗

2026-11-17InfoUpbit SDK v1.1.0 expands WebSocket data type support
Upbit released SDK v1.1.0 with broader WebSocket data type support.
Details

The entry '[업데이트] Upbit SDK v1.1.0 - WebSocket 데이터 타입 지원 확대' appeared about 29 days ago and is tagged Improved. It concerns the official SDK, not the raw websocket protocol. No action is needed unless we use the SDK.

Our handler: This is an SDK release; our handler connects directly to wss://api.upbit.com/websocket/v1.

Source ↗

2026-11-17InfoSelf-Match Prevention (SMP) default value applied
Upbit announced a default value for Self-Match Prevention on orders.
Details

The entry '[안내] 자전거래 체결 방지(Self-Match Prevention, SMP) 기본값 적용 안내' appeared about 1 month ago. SMP relates to order placement, which our handler does not use. No action is needed.

Our handler: SMP concerns trading order behaviour, outside the public orderbook and trade channels.

Source ↗

2026-11-17InfoTechnical indicators now supported over WebSocket
Upbit added WebSocket support for technical indicators.
Details

The entry '[안내] 기술적 지표 WebSocket 지원' appeared about 2 months ago and is tagged Added. It adds a new data type; existing orderbook and trade channels are not stated to change. No action is needed.

Our handler: A new indicator data type is additive and does not change the orderbook or trade channels we use.

Source ↗

Collected from the exchange's changelog and notices, summarized automatically; check the source before acting. All changes for this feed

Official documentation

Upbit — WebSocket orderbook (Korean) ↗docs.upbit.comUpbit — WebSocket trade (Korean) ↗docs.upbit.comUpbit — WebSocket guide: connection, PING, idle timeout (Korean) ↗docs.upbit.comUpbit — orderbook (REST, Korean) ↗docs.upbit.comUpbit — rate limits (Korean) ↗docs.upbit.comUpbit — changelog (Korean) ↗docs.upbit.com

Links go to the exchange's own documentation; it is theirs and may change. Our handler follows the version described above.