T212 API feedback

💡 Feature suggestions & ideas
1

Hello :waving_hand:,

I have been experimenting with the APIs recently and whilst you guys have covered most I would like to know if there is a roadmap on a few things that would make the API more appealing.

  1. Out of hours trading

    Extended hours of trading exist in the UI but currently not available at the API level

  2. Rate limit increases

    Current limit are.very restrictive you have to do a lot of retry logic to get to what you need. 3&4 could be good way to eliminate some calls.

  3. MOO/LOO order types (timing)

    instead of having all the client sending you an avalanche of order having a Market-on-open (MOO) and a Limit-on-open (Loo) so the broker handle the timing at opening and closing.

  4. Bracket order (structure)

    Bracket order would be a 3 in 1 Order , you buy at an entry (market or else) and then either a stop loss or a take profit

Having 3&4 would really make your APIs a great alternative to platform like Alpaca (docs.alpaca.markets/docs/orders-at-alpaca)

In the meantime we need to create complex OMS (Order management system) that are limited with rates of APIs.

Thanks team!

2

Regarding Rate Limits, I think you’ll get no joy. For my part (I use Visual Studio and http), I keep an in memory record of times and calls for each URL and put the app to sleep until it is next safe to call the endpoint again. This can be done because each call returns the rate limit in response headers.