Once the connection is successfully established, various requests can be made to the Websocket server.
Requests are made using JSON Objects, and responses are also JSON Objects.

Requests are divided into ticket field, type field, and format field, each consisting of the following components.

📘

Request format

[{Ticket Field},{Type Field},....,{Type Field},{Format Field}]

Ticket Field

To identify the data that you want to get, a value of 'ticket field' is required.

This value identifies the recipient of the market data and it is recommended to use a unique value (such as UUID).

Field Name
Type
Description
Required
Default
ticketStringA value that can identify youO

Type Field

In this field, you have to list the market data you want to receive.

"isOnlySnapshot" and "isOnlyRealtime" fields are optional and both snapshot and real-time data will be received if they are omitted.

Multiple {type field} can be specified for a single request.

Field Name
Type
Description
Required
Default
typeStringdata type
ticker: Current market price
trade: Transaction
orderbook: Orders
O
codesListMarket code list
*Must be requested in capital letters.
O
isOnlySnapshotBooleanOnly provides snapshot dataXfalse
isOnlyRealtimeBooleanOnly provides real-time dataXfalse

📘

'codes' in private data

For private data, if the codes field is omitted or requested as an empty array, you can receive information for all markets.

Format Field

If specified as "Simple", the response field names will be simplified. This is for reducing the traffic burden.

Field Name
Type
Description
Required
Default
formatStringFormat to receive
- DEFAULT: default format
- SIMPLE: simplified format
XDEFAULT