IBKR Client Portal Web API

Streaming WebSocket Data

Interactive Brokers Web API offers WebSocket streaming for market data, orders and pnl updates. To connect to the WebSocket follow the Getting Started Instructions to authenticate the gateway session. Once you receive the message "Client login succeeds" a websocket connection can now be established using the endpoint: wss://localhost:5000/v1/api/ws

There are two types of messages:

Solicited (↑↓): User has to explicitly send request to receive data.
Unsolicited (↓↓): User receives data without any incoming request.

Format for solicated message types: TOPIC+{ARGUMENTS}

The first letter of the topic determines, s=subscribe or u=unsubscribe
+ is used as a separator
Pass an empty argument {} if none is required
Each response relays back the topic of the request

Available Topics
Topic	Definition
Solicated Message Types
smd+conid / umd + conid	market data + contract identifier
sor / uor	live orders
spl / upl	profit and loss
ech+hb	echo + heartbeat
Unsolicated Message Types
system	system connection
sts	status
ntf	notification
blt	bulletin

Try the websocket connection here:

Note: Make sure to first launch gateway and authenticate.

wss://

{{ log.event }}: {{ log.data }}

Solicited Message Types

Market Data (Level I)

Using the Web API, you can request real time data for trading and analysis. For streaming top of the book (level I) data, the topic is smd+conid. The conid (contract identifier) uniquely defines an instrument in IBKR's database and is needed for many endpoints. To find the conid for a stock, the endpoint /iserver/secdef/search can be used, for futures /trsrv/futures and for options there is an additional step described here. For the topic: smd+conid it is required to specify the argument fields. The field value is a JSON Object which are a comma separated list of available tick types as described in the endpoint /iserver/marketdata/snapshot. Additional field values can be added to an existing market data request by resending smd+conid. To unsubscribe from market data, the topic is umd+conid.

Format: smd+conid+{"fields":[]}

Request:

ws.send('smd+265598+{"fields":["31","83"]}');

Received:

{
  "31": "382.89",
  "83": 0.04,
  "6119": "q6",
  "server_id": "q6",
  "conid": 265598,
  "_updated": 1593524408296, 
  "topic": "smd+265598",
}

Format: umd+conid+{}

Request:
```
ws.send('umd+265598+{}');
```

Live Orders

As long as an order is active, it is possible to retrive it using the Web API. For streaming live orders the topic is sor. When live orders are requested we will start to relay back updates. To receive all orders for the current day the endpoint /iserver/account/orders?force=false can be used. To unsubscribe from live orders, the topic is uor.

Format: sor+{}

Request:
```
ws.send('sor+{}');
```

Received:

{
  "topic": "sor" ,
  "args": [
    {
      "acct": "DU1234",
      "conid": 265598,
      "orderId": 922048212,
      "cashCcy": "USD",
      "sizeAndFills": "0/1",
      "orderDesc": "Buy 100 Limit 372.00 GTC",
      "description1": "AAPL",
      "ticker": "AAPL",
      "secType": "STK",
      "listingExchange": "NASDAQ.NMS",
      "remainingQuantity": 100.0,
      "filledQuantity": 0.0,
      "companyName": "APPLE INC",
      "status": "Submitted",
      "origOrderType": "LIMIT",
      "supportsTaxOpt": "1",
      "lastExecutionTime": "200708173551",
      "lastExecutionTime_r": 1594229751000,
      "orderType": "Limit",
      "side": "BUY",
      "timeInForce": "GTC",
      "price": 372,
      "bgColor": "#000000",
      "fgColor": "#00F000"
     }
   ]
}

Format: uor+{}

Request:
```
ws.send('uor+{}');
```

Live Order - Updates: When there is an update to your order only the change to the order is relayed back along with the orderId. Most commonly this would involve status changes and partial fills.

Received: Status Change(s)

{
  "topic": "sor" ,
  "args": [
    {
      "acct": "DU1234",
      "orderId": 352055828,
      "status": "PendingSubmit",
      "fgColor": "#3399CC"
     },
    {
      "acct": "DU1234",
      "orderId": 352055828,
      "status": "PreSubmitted",
      "bgColor": "#FFFFFF",
      "fgColor": "#0000CC"
     },
    {
      "acct": "DU1234",
      "orderId": 352055828,
      "status": "Submitted",
      "bgColor": "#000000",
      "fgColor": "#00F000"
     }
   ]
}

Received: Partial Fill(s)

{
  "topic": "sor" ,
  "args": [
    {
      "acct": "DU1234",
      "orderId": 352055828,
      "sizeAndFills": "100/622",
      "remainingQuantity": 622.0,
      "filledQuantity": 100.0,
      "avgPrice": "382.45",
     },
    {
      "acct": "DU1234",
      "orderId": 352055828,
      "sizeAndFills": "700/22",
      "remainingQuantity": 22.0,
      "filledQuantity": 700.0,
     },
    {
      "acct": "DU1234",
      "orderId": 352055828,
      "sizeAndFills": "722",
      "orderDesc": "Sold 722 Limit 382.40 GTC",
      "remainingQuantity": 0.0,
      "filledQuantity": 722.0,
      "status": "Filled",
      "timeInForce": "GTC",
      "price": 382.4,
      "bgColor": "#FFFFFF",
      "fgColor": "#000000"
     }
   ]
}

Profit and Loss

For existing positions it is possible to receive Profit and Loss updates to the Web API using the topic spl. In the payload response the daily profit and loss (dpl) and unrealized profit and loss (upl) are received as a total value for all positions. Updates are relayed back as quickly as once per second but can vary based on market activity. To unsubscribe from profit and loss the topic is upl.

Format: spl+{}

Request:
```
ws.send('spl+{}');
```

Received:

{
  "topic": "spl" ,
  "args": {
    "DU1234.Core": {
      "rowType":1,
      "dpl":-57520.0
      "upl":972100.0
    }
  }
}

Format: upl{}

Request:
```
ws.send('upl{}');
```

Echo

To maintain an active websocket connection the topic ech is used to send a hearbeat with the argument hb. It is advised to send a heatbeat at least once per minute.

Format: ech+hb

Request:
```
ws.send('ech+hb');
```
Received:
```
ech+hb
```

Unsolicited Message Types

System Connection

When initially connecting to websocket the topic system relays back a confirmation with the corresponding username. While the websocket is connecting every 10 seconds there after a heartbeat with corresponding unix time (in millisecond format) is relayed back.

Received:

{
  "topic": "system" ,
  "success": "user123"
}
{
  "topic": "system" ,
  "hb": 1594677336001
}

Authentication Status

When connecting to websocket the topic sts will relay back the status of the authentication. Authentication status is already relayed back if there is a change, such as a competing sessions.

Received:

{
  "topic": "sts" ,
  "args": {
    "authenticated": true
      }
{
  "topic": "sts" ,
  "args": {
    "competing": false
      }
}

Notifications

If there is a brief message regarding trading activity the topic ntf will be sent.

Received:

{
  "topic": "ntf" ,
  "args": {
    "id": INDICATIVE_DATA_SUGGESTION ,
    "text": "CFD quotes reference the trade, volume and bid/ask market data on the underlying STK" ,
    "title": "Warning" ,
    "url": "https://interactivebrokers.com/"
      }
}

Bulletins

If there is an urgent message concerning exchange issues, system problems and other trading information the topic blt is sent along with the message argument.

Received:

{
  "topic": "blt" ,
  "args": [
    "id": "" ,
    "message": "" 
    ]
}