For the current WebSocket request, you can optionally include a unique client request ID in the request body. The same client request ID will be found in the response and is used to match the response to the request. The client request ID must be a UUID.

We use a cross-leverage approach in our trading platform. This means leverage is applied at the account level rather than the trade level. As a result, if you use leverage on one open position, the same leverage must be applied to all subsequent positions until they are closed or open orders are canceled.

For order creation, this means that if you create an order with no specified leverage, a multiplier of 1 will be assumed. However, if you create an order with a different leverage multiplier (e.g., 10), you must explicitly include the value of 10 in the order creation payload.

URL

This stream can be subscribed per market and you will need to pass in the market in the URL query. See below.

Query params

market
string
required

Example value: ETH-USD. To get all supported markets, call /api/v1/markets endpoint.

Headers

See Authorization section on how to retrieve authorization token. Once token is received, set Sec-WebSocket-Protocol headers in the WebSocket handshake request or on connect().

Sec-WebSocket-Protocol
string
required

Example value (authorization token) :

authorization#eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdGFnaW5nLmZ1bmdpYmxlLnh5eiIsInN1YiI6ImQxM2I1MzBmLWFmNzMtNDBmOS04ZjhlLWVkNzk1OTU3YTU3ZiIsImF1ZCI6WyJzdGFnaW5nLWFwcC5mdW5naWJsZS54eXoiXSwiZXhwIjoxNzAzMzA1NzQwLCJpYXQiOjE3MDMzMDM5NDB9.vsHe4G_yEkRfz8XNoTKcX83udA-LUysWD4q80wfCC8k