// Note that both clientRequestId and leverage are optional
{
  "message": "createOrder",
  "content": {
    "clientRequestId": "0835bf3e-4a20-41f0-908d-8213f2b7a285",
    "price": "2000.90",
    "quantity": "1.00",
    "orderType": "buy",
    "tradeType": "limit",
    "leverage": "1",
    "postOnly": false // Optional
  }
}

// Order created successfully
{
  "resultType": "createOrder",
  "data": {
    "clientRequestId": "0835bf3e-4a20-41f0-908d-8213f2b7a285",
    "statusCode": 200,
    "body": "order accepted",
    "order": {
        "market": "ETH-USD",
        "orderId": "01HZ5J70FCBNJAS7TVPVB4GAAG",
        "orderType": "buy",
        "tradeType": "limit",
        "price": "3600",
        "quantity": "1",
        "leverage": "1",
        "createdAt": 1717100052972,
        "updatedAt": 1717100052972,
        "orderStatus": "active"
    }
  }
}

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 and open orders are canceled.

Please note that leverage must be specified in the create order request to ensure the correct leverage is applied. If the leverage value provided differs from the one currently set on the account, the order will be rejected. We recognize that this behavior may be a bit confusing, and we plan to introduce a separate endpoint in the future that will allow setting leverage at the account level.

We provide a post-only option for limit orders. When this option is set to true, the order will only be placed if it does not match with an existing order in the order book.

Using post-only orders will ensure that you are always the maker and never the taker.

If the order would match with an existing order, you will first receive a 200 response with resultType: createOrder, followed by a 400 response with resultType: rejectOrder.

For more details, refer to ourOrder Rejected Notifications

​
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

// Note that both clientRequestId and leverage are optional
{
  "message": "createOrder",
  "content": {
    "clientRequestId": "0835bf3e-4a20-41f0-908d-8213f2b7a285",
    "price": "2000.90",
    "quantity": "1.00",
    "orderType": "buy",
    "tradeType": "limit",
    "leverage": "1",
    "postOnly": false // Optional
  }
}

// Order created successfully
{
  "resultType": "createOrder",
  "data": {
    "clientRequestId": "0835bf3e-4a20-41f0-908d-8213f2b7a285",
    "statusCode": 200,
    "body": "order accepted",
    "order": {
        "market": "ETH-USD",
        "orderId": "01HZ5J70FCBNJAS7TVPVB4GAAG",
        "orderType": "buy",
        "tradeType": "limit",
        "price": "3600",
        "quantity": "1",
        "leverage": "1",
        "createdAt": 1717100052972,
        "updatedAt": 1717100052972,
        "orderStatus": "active"
    }
  }
}