Hi. I am new here, so I apologize if this question has been covered already.

Until recently I was trading on IBKR using the Client Portal API. Each day I would simultaneously place about 100 limit orders for various U.S. stocks, and I did this using the /orders REST endpoint. If one uses an array of orders as the payload of the post request, the orders are all submitted simultaneously.

Sadly, on Sept 4 IBKR stopped allowed one to submit multiple orders this way. Only single orders are allowed now. But if I try to submit ~100 orders sequentially, it will take too long. I need to submit them all within a few seconds of each other.

So, I am considering using the TWS API for this. My questions are:

1. Is it possible to simultaneously place ~100 limit orders using TWS API (with ib-async)? If yes, how?

2. In case people here are familiar with the Client Portal API, does anyone know an alternative way to submit simultaneous orders with the Client Portal API? (I submitted this question to IBKR, but there is no reply.)

Thanks very much for any guidance that anyone can give me.

Aside from the TWS API's inherent limitation of 50 messages per second implying a maximum of 50 orders per second being sent to the TWS, there are no further API-only limitations. Interactive Brokers however requires its users to monitor their Order Efficiency Ratio (OER) as detailed in the Considerations for Optimizing Order Efficiency IBKB article.

Additionally, please note IB allows up to 20 active orders per contract per side per account.

()

Thanks very much for that information. Does one really need to submit the orders sequentially? Is there no way to submit a batch of orders at one time? I would have thought that many IBKR users would need to do this (likewise with cancelling a batch of orders).

I notice something called the One-Cancels All (OCA) order type:

Is it possible somehow to use that to submit a batch of orders?

There is no batch order submission message/request in TWS API.? Order management is described at

Orders are submitted to TWS/IBGW one at a time through the request. That is true for single orders as well as multi-order constructs such as bracket orders or of Once-Cancels-All groups.

You may be able to place your orders well ahead of when you want them to trigger if the available are powerful enough to implement your logic. Conditional orders are resting within the IBKR infrastructure and as such much closer to the exchange than your client or TWS/IBGW.

闯ü谤驳别苍

开云体育

I don't use REST API but read about it, so here are thoughts:

I don't have idea of the time real TIME TROUGH for REST calls, generally theses kind of things are implemented atop existing infra and I won't be surprised that what is a batch for you is serialized by IBKR upon arrival. (I can even imagine this as a reason they stop supporting batch mode, it may even be processed out of sequence for good reasons but difficult to report)

?

The API is quit fast and give you more control about what happens, so you should try and compare the API to any real info or guesstimate of REST TT of orders to the system.

?

Alternative: IBKR FIX interface,

theoretically it's the fastest way to order in. But I don't saw/see any simple way to benchmark it.

It's tedious to setup, the complexity lies more in the "pipe" system as you need to setup a VPN and alike proxies related to authentication, from what I remember IBKR allows a local VPN for emul and FIX have debug flags.

While still being a 'one man' mission level. I don't recommend trying FIX before you evaluate if the API is enough

And before entering the FIX world you should consider the extra work it requires to be sure of the payback. My tests+pain did drove me back to API which is enough for me, as ds-avatar rightfully wrote it, you most likely have exogenous pacing reasons.

But... it exist.

?

Thanks everyone for the very helpful information. This will get me pointed in the right direction. I will try placing the orders sequentially with TWS API.