Investing in financial products involves risk to your capital.

Close Navigation
Learn more about IBKR accounts


Getting Started

FIX Integration efforts are handled by the Interactive Brokers (IBKR) Fix Engineering team (who can be reached at For a basic understanding of FIX protocol, its history, and its uses, please review this link:

To view the IB FIX Specification Guide, go to and select “I agree” under the section “FIX/CTCI Users’ Guide Disclaimer” at the bottom of the page.

While Interactive Brokers does follow the FIX standard, it is important to remember that all FIX tags from 5000-9999 are custom values. As such, it is recommended to review the IBKR FIX Manual to inspect unique tags to Interactive Brokers.


Important Notes:

  • IB FIX sessions are order routing sessions only. Market data and account data subscriptions are handled by the TWS API.
  • Clients who wish to begin FIX integration with IBKR are required to have a minimum funded balance of $10,000 USD.
  • Client’s IBKR account will be subject to IB’s per-session monthly minimum commission fee of USD $1,500 per month for the first FIX session and USD $1,000 per month minimum commission for any subsequent session(s). Meaning – if the trading commissions do not add up to $1,500 (or monthly fee based on how many sessions you have), IBKR will assess any shortcoming up to $1,500 (or monthly fee based on how many sessions you have).  Details are listed here.
  • FIX Integration is limited to IBKR Pro clients. IBKR Lite clients are not permitted to route orders via FIX, which some exceptions for introducing brokers.  Please inquire with the Client Integration team if you are an IBKR Lite broker seeking to route orders via FIX.

FIX vs. TWS session usernames

Clarification on the usernames and “sessions” involved in using the TWS API alongside FIX:

  1. Once a given username is configured for FIX session use, it cannot be used as a “normal” IB username to log into various platforms like TWS, IB Gateway, or Client Portal.
  2. Consequently, to use the TWS API alongside FIX, you’d want to set up a another username which will remain a normal “TWS session” username, and that’s the username/password that you’d use in IB Gateway’s “Market Data” login fields beneath the “FIX Login” at the top:
  3. Note that despite the “Market Data” label, this session is exactly the same as logging in via the “IB API” tab (or even logging into TWS itself). You have access to the whole TWS API featureset, not just market data.
    IB Gateway Showing the Fix Login page
  4. This TWS API username would also be the username that should carry any market data subscriptions you intend to use alongside the FIX session (IB usernames carry market data permissions, not the account IDs themselves).
  5. You’d probably want to create this TWS API username at the “top” of your account structure so it can see e.g. portfolio data for all of your accounts, but you don’t need to give it trading permissions on those accounts. And if you only intend to consume market data via this username, it doesn’t even need to be able to see all of the other accounts in the structure. (For example, I’ve seen a non-pro advisor structure where orders were sent via a master-level username, but all market data was consumed via one of their subaccount usernames.)
  6. In addition to the additional TWS API username, I would also recommend preserving the original, top-level username of the linked structure for all other non-API/non-automated usage. That is, you can log into TWS with that username to watch activity in your accounts, leaving the TWS API username solely for automated use. Overall this would mean three usernames: one for manual interaction, one configured for FIX, and one set aside for TWS API use.
  7. Documentation for creating additional usernames for the primary accountholder:

FIX Order Routing Basics

Interactive Brokers offers connectivity via FIX protocol for the purposes of routing orders. Market data and account data subscriptions are handled by the TWS API. If a client prefers to route orders via FIX and market data/account data is a requirement, they will need a second TWS configured user linked to that account.

Note that all FIX integration testing is done in the IB QA system. IBKR’s Paper Trading accounts are not compatible with FIX.

A client is encouraged to review the $1500/month minimum commission requirements that IB imposes on clients with a FIX session linked to their production account.  Please review the special connections section of the Required Minimums page.  More details can be found here.

FIX Integration Testing in QA

The general procedure for implementing a FIX connection is as follows:

  1. The Client Integration Team creates a test FIX session for each client in our QA system.
  1. The client will begin independent message testing to identify what message configurations, formats, values etc., if any, need to be changed.
  1. When both the client and the Client Integration Team are comfortable with the FIX messaging, a supervised FIX certification test with a Client Integration Team member is scheduled. The certification test will replicate all order types, instructions, etc., that the client plans to send in production. The test will also include unsolicited cancels, simulated trade busts, and recovery testing (simulated line failure).
  1. Upon successful completion of the certification test, IBKR will begin converting an existing production TWS user to FIX. Once converted, connectivity is tested to the FIX session to verify that heartbeats are successful following the connectivity test, the client will place a handful of small test orders, resulting in executions. If everything works correctly, production order flow can continue at the pace chosen by the client.

Supported Network Connectivity Options for FIX clients in Production

  • Equinix Cross Connect (must be approved by IB management): IBKR supports intra-datacenter cross-connects at Equinix’s global datacenters: NY5 in Secaucus NJ, HK3 in Hong Kong, ZH4 in Zurich, and CH4 in Chicago. Clients who have a presence within these datacenters can order a cross-connect from the datacenter to IBKR’s cage there. The client is responsible for the costs of the cross-connect. Once the client orders the cross-connect, IBKR’s network engineers will work with the client and the datacenter.
  • VPN (must be approved by IB management): IB supports hardware VPN tunnels from the client site to IBKR. Network engineers on the client side will work with the IBKR network group to share keys, and configure routers. VPN connections are for FIX clients only. IBKR does not support VPN connectivity for TWS users.
  • Leased line/Dedicated line: A dedicated network line from the client site to IBKR. The client must contact a local telecommunications company to get pricing and place an order. The IBKR network team will assist the telecommunications firm with the installation. IBKR’s global datacenters with client points of presence are: NY5 in Secaucus NJ, HK3 in Hong Kong, ZH4 in Zurich, and CH4 in Chicago.
  • Extranet: A network firm such as Radianz or TNS controls privately owned networks of dedicated lines to manage a connection from client site to IBKR. The IBKR network team will work with the extranet firm on the installation. The client is responsible for contacting the extranet providers, owning, and paying for the line.
  • IB Gateway client: A lightweight java application that the client installs on the machine that houses the FIX engine (or another machine on the client’s network), and that connects to IBKR via a tunnel created over the internet, with data encrypted. The client connects their FIX engine to a port that the IB Gateway client is listening on, and the connection is passed through the tunnel created by the gateway to IBKR. The IB Gateway client does not have an auto login feature. It requires a manual login each day with a username and password. Here is a link containing information on the IB Gateway client:

This website uses cookies to collect usage information in order to offer a better browsing experience. By browsing this site or by clicking on the "ACCEPT COOKIES" button you accept our Cookie Policy.