Channel, Event and Model
Data such as orderbook, ticker and last transactions are not sent directly after connection or user login is made.
There is a specific channel and event for each process. By subscribing to these channels and events, this data is received.
Once subscribed to a channel, the server sends events to that channel continuously to the client, unless the unsubscribe message is sent.
On the server, the channels generally represent the places where the transaction takes place (orderbook,last transactions, etc.) and the events represent the pair value (such as BTCTRY, ETHTRY, XLMUSDT) where the transaction takes place.
In some exceptional cases, these values may change. For example, to receive ticker data for all pairs, it is necessary to subscribe to the event of the ticker channel.
The server runs on 3 channels;
| Channel | Description |
|---|---|
| orderbook | Sends the transactions in the order book. The event name is the upper-case name of the pair. Ex: BTCTRY |
| trade | Sends data for recent transactions. Depending on the data type, incoming data can be individual or aggregated. The event name is the upper-case name of the pair. Ex: BTCTRY |
| ticker | Sends the current ticker data. There are two types of events. In the all event, the data for all pairs comes. To receive only events of a particular pair, you must subscribe to the upper-case pair name event. Ex: BTCTRY |
For use on browsers or platforms where WebSocket is not supported, it is also possible to access data sent via WebSocket with specific endpoints.