I have had a Tradovate API implementation for long time and it worked well. Recently I have rewritten it to an abstracted API where it runs as a separate service that is always on. This gives you the ability to restart your “Bot” service without impacting your Tradovate Websocket connections.
You communicate with this “Proxy Service” using websocket commands, but it abstracts all the Tradovate specific details out. This allows you to create different implementations for different brokers and then use a single / common API to control them all in a consistent manner. Your events for fills, rejects, etc are exactly the same for all brokers so the code does not have to understand or deal with the differences between brokers.
The only difference is when you link the user accounts.
So I wonder if there is any interest for such a common API specification? Would other developers implement the spec for brokers, other than Tradovate (since I already have an implementation for Tradovate)? This could mean that there is a single way to create bots that can trade many brokers without every bot developer reinventing the wheel.
One option is to Open Source this, but I am not ready to support noobs asking obvious questions because they did not read the docs.
Another is to offer it as a service where bot developers can use the APIs without having to go through the pain of implementing broker APIs. This is way better than your typical webhook where you trigger a trade and then pray that it works out. This give you active trade management for the life of the trade.
I am not sure what my plan is with this project, other than internal use… but thought of polling other developers for feedback.