Build an IB Fix development environment for IB Fix development, ibfix
Interactive Brokers (IB), a world-renowned Internet brokerage, opens an account at IB to trade a variety of global financial products (stocks, futures, foreign currency ...)
Many small Internet brokers in China (including some small start-up financial technology companies) mostly (not all) choose IB as the downstream brokers of US stocks (generally speaking: all U.S. shares are placed on the IB channel)
In most cases, apart from the stability and reliability of IB, the cost is mainly considered (IB charges are more reasonable, and the specific charging standards are described in detail on the official IB website)
Generally, there are two methods to connect to IB:
(1) ib api. API supports interfaces in multiple languages, such as JAVA, C #, and Python.
The API development process can generally be attributed to: API calling service + TWS
(2) ib fix. FIX development should be the most standard method in the industry (mainly because the FIX protocol is widely used around the world)
The FIX development process can generally be attributed to: FIX implementation service + IB Gateway
Because FIX is a standard solution in the industry, these blog posts mainly introduce ib fix development.
To facilitate the description, assume that A small Chinese Financial Technology Company A wants to connect to IB, that is, Company A wants to trade U.S. shares through IB.
Before launching ib fix development, Company A needs to build A test environment for FIX development. The test environment mainly includes the following steps:
(1) Company A must first open A real-disk account in IB (the assets of this account must be at least USD 10000)
(2) Company A should contact ib qa Department to apply for A testing environment from QA.
(3) After receiving the application, QA will check the funds of A's real-disk account. If the funds are greater than or equal to $10000, QA will
A sends the "FIX Intergration Information.pdf" file (this file is equivalent to the questionnaire survey required by user)
This questionnaire is intended for IB to learn about the types of financial products that users trade through IB, the connection methods of users, and the handling methods entrusted after disconnection.
(4) After the above files are filled in, ib qa will open the test account name and password for IB Gateway, and the test account and password for TWS.
(5) Developers of Company A download the IB Gateway and TWS software and replace the jts. ini file with the file provided by QA under the installation path of IB Gateway.
Company A developers use the test account and password to log on to the Gateway and TWS. If the logon succeeds, the test environment is successfully established.