- Joined
- 2/8/18
- Messages
- 2
- Points
- 13
Hello everyone,
I have been thinking of building open source vendor agnostic financial API for market data and order execution for about a year or two now. I finally decided to do it. The result is ZMAPI. It has fully functional market data (MD) support as of this moment. I have programmed three different connector modules to connect with three different vendors: Interactive Brokers TWS API, CTS T4 API and Bitstamp API. New connector can be added as required and I encourage people to contribute more connectors as the demand for them arise.
Account and execution side (AC) will be built in the future. I haven't started working with that yet and I'm now trying to come up with a good architecture. Any help with the architecture design will be very welcome.
Features:
- uniform API
- combining the best sides of all the vendors, abstracting away poor architecture
- modular design, middleware modules are used to provide uniformity
- vendor agnostic, no need to marry one vendor
- cross platform
- free
- open-source
- ØMQ is used for messaging
- language agnostic, accessible with every programming language
ZMAPI GitHub Page
ZMAPI Wiki
Bitstamp Tutorial
More tutorials coming soon...
----------
Pull requests, new ideas and comments are very much appreciated. Architecture can still be changed if there is a need as there are no real users yet, it's a brand new API. I'm open to suggestions.
Also looking to have some dedicated developers in the ZMAPI organization that will form the core team. Let me know if you have programming skills and are interested in being part of this.
I have been thinking of building open source vendor agnostic financial API for market data and order execution for about a year or two now. I finally decided to do it. The result is ZMAPI. It has fully functional market data (MD) support as of this moment. I have programmed three different connector modules to connect with three different vendors: Interactive Brokers TWS API, CTS T4 API and Bitstamp API. New connector can be added as required and I encourage people to contribute more connectors as the demand for them arise.
Account and execution side (AC) will be built in the future. I haven't started working with that yet and I'm now trying to come up with a good architecture. Any help with the architecture design will be very welcome.
Features:
- uniform API
- combining the best sides of all the vendors, abstracting away poor architecture
- modular design, middleware modules are used to provide uniformity
- vendor agnostic, no need to marry one vendor
- cross platform
- free
- open-source
- ØMQ is used for messaging
- language agnostic, accessible with every programming language
ZMAPI GitHub Page
ZMAPI Wiki
Bitstamp Tutorial
More tutorials coming soon...
----------
Pull requests, new ideas and comments are very much appreciated. Architecture can still be changed if there is a need as there are no real users yet, it's a brand new API. I'm open to suggestions.
Also looking to have some dedicated developers in the ZMAPI organization that will form the core team. Let me know if you have programming skills and are interested in being part of this.