Now it is very difficult to find a broker who allows passive earnings on computer trading. It is much more profitable and safer to trade on your own.
I don't get it. What is the point of asking this question? Why would you want to use a REST api for trading? Whether it is possible to submit 200 orders in one minute depends on your broker, and has nothing to do with REST.
because I am thinking about using other brokers for free commission, e.g., tdameritrde and etrade. I found more and more brokers provide REST plus websocket access. it looks like the two technologies would be the main stream in the near future for customer trading access.
I'm thinking about using other ways of getting to work, like using an electric vehicle like tesla or volt. Anyone have any experience driving to work in a red painted car? I hear more and more people are using red cars for their drive to work. Can you do 0-60 in under 10 seconds in a red car?
I had experience trading in such a spirit. I can only say that here almost everything depends on which broker to work with.
No need to jump ship just because this might be the future. We can jump when it becomes main stream. Also they are easy to switch to.
There's 1 key advantage of a REST API over C++ or .NET SDK that no one mentioned earlier. A SDK requires you to install an external client library, while a REST API doesn't. This is important if you work at a large institution and every install and update needs to go through infosec compliance and a code audit. (This is also why signed Conda packages is a thing.)
It's a good point, but technically this benefit doesn't have anything to do with REST itself. It comes purely from the fact that REST is built on top of HTTPS, and most languages have a client built in. If your language doesn't (e.g. C++), you still need an external library. Some aspects of real REST, like statelessness, don't really make sense for serious trading. Any open source protocol (e.g. FIX) over a secure socket could provide the same benefit without the disadvantages.