Knowledge Base

Exchange name change

Overview:

Interactive Brokers is completing an effort to update and consolidate exchange names where appropriate. When this effort is complete, the following updates will be in effect:

GLOBEX and CMECRYPTO will be consolidated to a single exchange, ‘CME’
ECBOT will be updated to ‘CBOT’
COMEX listed metals (previously reflected as NYMEX) will be updated to exchange ‘COMEX’
NYMEX, no change

Given the breadth of products involved, we are migrating in four waves based on underlying products:

Key	Effective Trade Date	Products
Wave 1	October 30, 2022	GLOBEX: ZAR, LB, DA, IXE
Wave 2	November 6, 2022	GLOBEX: EMD, BRE, CHF, SOFR3, E7, NKD CMECRYPTO: BTCEURRR, ETHEURRR, MET
Wave 3	November 13, 2022	GLOBEX: All remaining products CMECRYPTO: All remaining products ECBOT: ZO, ZR, 2YY, 30Y NYMEX: ALI, QI, QC
Wave 4	December 4, 2022	ECBOT: All remaining products NYMEX: All remaining "Metal" products

I am trading via API, how does this impact me?

For API clients the only requirement would be to provide a new exchange name, for example: exchange=”CME”, for existing contracts for the affected exchanges.

Old exchanges names will no longer be available after the change.

More details can be found within our FAQs through the following link: Upcoming Exchange name Changes

Note: If you are using a third party software connected to TWS or IB Gateway and that software does not recognize the new contract definitions, please contact the third party vendor directly.

If you use RSA encryption in file exchange communication with Interactive Brokers, best practice requires that this key be backed up for security and retrieval purposes. Creating a backup is quick and ensures the longevity of your Key Pair.

Note: this tutorial assumes you have already set up a Key pair. If you need guidance to set up the Key pair please refer to this article, which is a prerequisite to the instructions below.

Please select one of the below links, according to your Operating System:

Windows
macOS

Windows

1. Launch the application Kleopatra and select the encryption key you want to transfer. Then right-click on the selection and choose Backup Secret Keys...

Note: Do NOT use Export..., as this will only export the public part of the Key while you need to have a backup of both public and private parts.

2. Select a folder of your preference (e.g. Desktop) and a file name of your preference (e.g. secret-key-KEYID.asc) for your backup copy. Then click Save.

3. Enter the passphrase you have set when you created the Key and click OK.

4. A pop-up will confirm the backup has been successfully created. Click OK.

macOS

1. On the machine where the encryption keys are stored, create a new folder (e.g., on your Desktop).

2. Launch the application GPG Keychain and select the encryption key you want to transfer. Please make sure that Sec/Pub is indicated in the Type column.

3. Click the icon Export on the top toolbar. In the field Where, select the folder you previously created. Make sure to check Include secret key in exported file and then click Save as illustrated in the above screenshot.

4. A backup copy of the key pair will be created in the folder you selected.

Related articles

KB3842 - Using GPG/RSA encryption keys to guarantee the privacy and security of your Reports
KB3968 - Generate a key pair using GPG for Windows
KB4205 - Generate a key pair using GPG Suite on macOS
KB4108 - Decrypt your Reports using GPG for Windows
KB4210 - Decrypting Reports using your PGP Key pair on macOS
KB4407 - Generate RSA Key Pair on Windows

KB4578 - How to Access your Reports using FTP on Windows

KB4580 - How to Access your Reports using FTP on MacOS

KB4410 - How to set up sFTP for using Certificate Authentication on macOS
KB4323 - How to transfer your public/private key pair from one computer to another

How to Set Up sFTP for Using Certificate Authentication on macOS

These instructions apply to users who are receiving their statements via sFTP. If you elected to receive your statements that way, you would first need to generate an RSA Key pair. If you need guidance to set up the Key pair, please refer to this article, which is a prerequisite to the instructions below.

Note: There are many sFTP Clients available for macOS, either licensed or freeware. In this procedure we will refer to FileZilla, which is free of charge, but you can use a different one. FileZilla for macOS can be downloaded here.

1. Once you have installed FileZilla, launch it.

2. Click on File in the top left and select Site Manager:

3. If you see an existing Interactive Brokers sFTP site in the list, jump directly to point 6. If you do not have such site configured yet, Click New Site and select SFTP – SSH File Transfer Protocol as Protocol:

4. Change Logon Type from Normal to Key File and click on Browse to select the corresponding Private Key file from the designated directory where it is saved.

5. Enter:

xfer.interactivebrokers.com in the Host field.
32 in the Port field.
The username given you by Interactive Brokers in the User field.

6. Click Connect. Once successfully connected, you will be able to drag files from the Remote site (right side panel) to the Local machine (left side panel). In this way you will download the files on your local machine.

Common issues and solutions

A. The Login Credentials Provided are Incorrect

Ensure the correct login details are being used to connect to the sFTP server. The username and password you are entering should match the ones you have received from the Reporting Integration Team.
Confirm you have configured your sFTP Client to use the Private Key file for the logon authentication (see step 4. of the above procedure.)

B. Server Refused Our Key

Try accessing the sFTP server using a different Client (FileZilla, WinSCP, CyberDuck, ect.)
Ensure the Private Key file being used to Authenticate the server login attempt is related to the Public Key you originally sent to the Reporting Integration Team.
Should the above checks be unable to resolve the issue, please generate a new RSA Public/Private Key pair and send only the Public part to the Reporting Integration Team, as per IBKB3842.

C. Connection Timed Out

In case you have an antivirus or a security software installed on your machine, make sure it is not blocking the FTP connection attempt. Normally, security software allows to set up exceptions for specific connections in order to whitelist them.
Verify that the public IP Address of the machine running the sFTP client, is the same you have originally provided to the Reporting Integration Team for being whitelisted. You can discover your public IP Address by searching the Internet for “what is my IP”. If your current IP Address is not the same you provided to us, please send it to our Reporting Integration Team for being whitelisted.
Ask your network administrator/s to confirm that your firewall allows both incoming and outgoing traffic from/to xfer.interactivebrokers.com on port TCP 32.
Should the above steps be unable to resolve the issue, please generate a new RSA Public/Private Key pair and send only the new Public part to our Reporting Integration Team, as per IBKB3842.

Related articles

KB4819 - How to set up sFTP for using Certificate Authentication on Linux

KB4578 - How to Access your Reports using FTP on Windows

KB4580 - How to Access your Reports using FTP on MacOS

KB4409 - How to set up sFTP for using Certificate Authentication on Windows
KB4411 - How to backup your public/private Key pair
KB4323 - How to transfer your public/private key pair from one computer to another

How to Set Up sFTP for Using Certificate Authentication on Windows

1. Start WinSCP.

2. Click on Session and select New Session.

3. If you see an existing Interactive Brokers sFTP site in the list, select it and jump directly to point 5. If you do not have such site configured yet, enter:

xfer.interactivebrokers.com in the Host name field.
32 in the Port number field.
The username provided to you by Interactive Brokers in the User name field.

Select SFTP as File protocol:

4. To ensure the session is using the appropriate Private Key file, Click Advanced > Authentication. Verify that the Private Key file field has the appropriate Key file selected. Click OK.

5. Click Login to connect with the sFTP host and retrieve reports in clear text.

6. Drag documents from the right side panel (sFTP host site) to the left side panel (local machine host).

Common issues and solutions

A. The Login Credentials Provided are Incorrect

Ensure the correct login details are being used to connect to the sFTP server. The username and password you are entering should match the ones you have received from the Reporting Integration Team.
Confirm you have configured your sFTP Client to use the Private Key file for the logon authentication (see step 4. of the above procedure.)

B. Server Refused Our Key

Try accessing the sFTP server using a different Client (FileZilla, WinSCP, CyberDuck, ect.)
Ensure the Private Key file being used to Authenticate the server login attempt is related to the Public Key you originally sent to the Reporting Integration Team.
Should the above checks be unable to resolve the issue, please generate a new RSA Public/Private Key pair and send only the Public part to the Reporting Integration Team, as per IBKB3842.

C. Connection Timed Out

In case you have an antivirus or a security software installed on your machine, make sure it is not blocking the FTP connection attempt. Normally, security software allows to set up exceptions for specific connections in order to whitelist them.
Verify that the public IP Address of the machine running the sFTP client, is the same you have originally provided to the Reporting Integration Team for being whitelisted. You can discover your public IP Address by searching the Internet for “what is my IP”. If your current IP Address is not the same you provided to us, please send it to our Reporting Integration Team for being whitelisted.
Ask your network administrator/s to confirm that your firewall allows both incoming and outgoing traffic from/to xfer.interactivebrokers.com on port TCP 32.
Should the above steps be unable to resolve the issue, please generate a new RSA Public/Private Key pair and send only the new Public part to our Reporting Integration Team, as per IBKB3842.

Related articles

KB4819 - How to set up sFTP for using Certificate Authentication on Linux

KB4578 - How to Access your Reports using FTP on Windows

KB4580 - How to Access your Reports using FTP on MacOS

KB4410 - How to set up sFTP for using Certificate Authentication on macOS
KB4411 - How to backup your public/private Key pair
KB4323 - How to transfer your public/private key pair from one computer to another

Consideraciones de seguridad luego de optar por dejar de usar el sistema de acceso seguro

Overview:

Los titulares de cuentas que hayan optado por dejar de usar el sistema de acceso seguro (SLS) de IBKR efectivamente renuncian a las protecciones que ofrece la autenticación en dos factores. Se le recomienda enfáticamente utilizar medidas de seguridad alternativas, siendo una de ellas las restricciones de IP. Al seleccionar esta configuración mediante Client Portal, le estará diciendo a Interactive Brokers que solo desea acceder a sus plataformas de negociación desde una dirección de IP específica. Además, en caso de tener varios operadores autorizados para una determinada cuenta, estas restricciones podrán configurarse a nivel de operador individual a través del usuario principal de la cuenta.

Lista de comprobación preliminar>

Antes de configurar las restricciones de IP, deberá:

Conocer su dirección de IP WAN. Esta es la dirección de IP expuesta en el lado externo (Internet) de su red, y es distinta de su dirección de IP local (denominada también dirección de IP LAN). Si opera desde las oficinas de una empresa, puede solicitarle a su departamento de informática o de redes la dirección de IP WAN de su ordenador. Si se conecta a la Internet a través de una conexión privada de banda ancha, cable o satélite, puede obtener esta información de su proveedor de servicios de internet (ISP).
Asegúrese de que su dirección de IP sea estática. Esto significa que su dirección de IP siempre será la misma, y que no cambiará luego de reiniciar el enrutador o módem luego de un determinado periodo. Las mismas entidades que le proporcionaron la dirección de IP WAN podrán confirmarle si se trata de una dirección estática o dinámica.
Tenga en cuenta que las restricciones de IP no tienen efecto inmediato. Nuestros sistemas aplican filtros durante su reinicio trasnoche a diario. Pueden tardar hasta 24 horas para que estén activas, dependiendo del momento en el que envíe su solicitud de restricciones de IP. Lo mismo se aplica cuando modifica o elimina restricciones de IP existentes. Asegúrese de tener esto en cuenta cuando planifique sus medidas a tomar.
Las restricciones de IP se aplicarán para TODAS las plataformas de negociación que ofrece IBKR. No afectará el acceso a Client Portal, el cual seguirá siendo accesible desde cualquier dirección de IP.

Nota:

Tenga en cuenta que existe la capacidad técnica de indicar malinterpretar la dirección de IP, y la protección total de la cuenta solo se garantiza utilizando la autenticación en dos factores del sistema de acceso seguro (SLS) (ibkr.com/sls).

Si tiene inquietudes respecto de esta cuestión, no dude en contactar con el centro de asistencia técnica de IBKR.

Cómo configurar las restricciones de IP:

Inicie sesión en Client Portal y haga clic en el icono del menú
Desde el menú, haga clic en Configuración y luego en Configuración del usuario. Luego, haga clic en el icono del engranaje (configurar) junto a Restricciones de IP.
Verá una breve descripción de los efectos de las restricciones de IP. Para configurar una nueva restricción de IP, haga clic en Añadir restricción de IP.
Seleccione Operador desde la lista desplegable e ingrese la dirección de IP (en el formato xxx.xxx.xxx.xxx) que desea permitirle a su operador. Luego, haga clic en Continuar.
Si inició sesión en Client Portal sin utilizar la autenticación en dos factores, recibirá un correo electrónico ¹ con un número de confirmación. Ingréselo en el campo Número de confirmación. Una vez que haya hecho esto, haga clic en Continuar para enviar la solicitud. Si se conectó a Client Portal utilizando un dispositivo de acceso seguro, continúe directamente con el punto 6.
Si la operación se realizó correctamente, verá una ventana de confirmación. Haga clic en Aceptar.
El sistema le mostrará una lista con sus restricciones de dirección de IP activas. En caso de que desee crear una adicional, haga clic nuevamente en Añadir restricción de IP, de lo contrario abandone esta sección

Opción de no usar el sistema de acceso seguro y restricciones IP para operadores de penny stocks (acciones especulativas):

Los clientes que hayan optado por no usar el sistema de acceso seguro, y solo utilicen la autenticación en dos factores para Client Portal, deberán activar las restricciones de IP para poder activar los permisos de negociación para penny stocks.

Mejores prácticas adicionales para asegurar su ordenador y su red:

Al iniciar sesión en TWS, active la casilla "Usar SSL" en la ventana de acceso. El sistema SSL (Secure Socket Layer) garantiza que toda la información intercambiada entre su ordenador y nuestros servidores esté protegida utilizando un cifrado de 128-bit.
Utilice un cortafuegos para evitar accesos no autorizados a los servicios expuestos por su red u ordenador. Durante la configuración del cortafuegos, asegúrese de autorizar los hosts/puertos que se indican en la sección TWS DE ESCRITORIO en el artículo KB2816.
Utilice software antivirus para identificar y eliminar virus que pudieran haber afectado su ordenador. Debido a que se crean nuevos virus constantemente, deberá actualizar la base de datos de amenazas de su software antivirus regularmente.
Utilice software para programas informáticos malintencionados (malware) para detectar y eliminar programas de espía o malintencionados (spyware/malware) que puedan recopilar distintos tipos de información personal, controlar su actividad de búsqueda e interferir con el control de su ordenador. Hoy en día, las soluciones antivirus incluyen una protección contra programas informáticos malintencionados incorporada.
Evite utilizar conexiones inalámbricas (Wi-Fi) que sean públicas, no seguras o que no estén operadas por usted. Si utiliza una red no segura (p. ej., zonas de cobertura inalámbrica públicas), deberá evitar conectarse a cuentas de instituciones financieras que posea, lo que incluye su cuenta de IBKR.

Notas:

1. Si no ha recibido el correo electrónico, asegúrese de que no esté en la carpeta de correo basura (spam) de su casilla de correo, y será conveniente que añada las direcciones de correo electrónico donotreply@interactivebrokers.com y help@interactivebrokers.com a la lista de remitentes de confianza. Puede solicitar que se le envíe un nuevo correo electrónico pulsando el botón Reenviar número de confirmación.

SEC Tick Size Pilot Program FAQs

Tick Size Pilot ("TSP" or "Pilot") Program:

Under the TSP Program, if IBKR receives any order in a Pilot Security that does not conform to the designated pricing increment (e.g., a limit price in a $0.01 increment for a security designated as trading $0.05 increments), IBKR will REJECT that order, subject to limited exceptions. IBKR strongly encourages a thorough review of your software or your vendor’s software to understand the criteria for what causes an order in a Pilot Security to be rejected to permit you or your vendor to make changes to correctly handle orders in Test Group Pilot Securities.

FREQUENTLY ASKED QUESTIONS:

Q: Is the Tick Size Pilot program still ongoing?

A: On March 29, 2019 the data collection requirements under the National Market System (NMS) plan to implement a Tick Size Pilot Program (Tick Size Pilot) ended. As a result, the Pilot Security File and Change File will no longer be produced on a daily basis. At the conclusion of the pilot, a blank Tick Size Pilot Securities file will be produced and the Change File will be updated to show the deletion of securities from the Tick Pilot Size list.

Q: What is the Tick Size Pilot?
A: On May 6, 2015, the SEC approved an amended TSP NMS Plan. The Pilot will be two years in length. Data collection for the Pilot began on April 4, 2016, 6 months prior to the implementation of the trading and quoting rules for the Pilot. Implementation of the trading and quoting rules for the Pilot will begin on October 3, 2016.

The Pilot will be conducted using a Control Group and three Test Groups where variations in quoting and trading rules exist between each group. Please see the TSP NMS Plan for additional information.

Q: Will the Pilot quoting and trading rules apply during regular market hours, pre-market hours and post market hours?
A: The Pilot rules apply during all operational hours (pre-market, regular hours, and post market hours trading).

Q: Will the Pilot quoting and trading rules apply to odd-lot and mixed-lot sizes?
A: Yes, the Pilot rules to all order sizes.

Q: Will orders in Control Group Securities be accepted in price increments of less than $0.05?
A: Yes, orders submitted in price increments of less than $0.05 will continue to be accepted in Control Group securities.

Q: Will orders in a Test Group 1, 2 or 3 Pilot Securities be accepted in price increments of less than $0.05?
A: No, unless covered by an exception, orders submitted in price increments of less than $0.05 will be rejected.

Q: Which Pilot Security Orders in Test Groups will Interactive Brokers accept at other than $0.05 increments?
   Midpoint orders with no explicitly stated limit price or impermissible offsets will be accepted
       VWAP orders that do not have an explicitly stated limit price or impermissible offsets will be accepted.
       Interactive Brokers will accept Exchange operated Retail Price Improvement orders as follows:
               Test Group 1 in $0.001 price increments
                 Test Groups 2 and 3 in $0.005 price increments.

Q: Will there be any changes to the Opening / Closing processes on Exchanges?
A: Please refer to each of the exchange rules for details but in general, there will be no changes to the Opening / Closing process. All orders entered and eligible to participate in Exchange Opening / Closing Cross will be accepted in increments of $0.05. The Exchanges will begin publishing all quotes in increments of $0.05; however, Net Order Imbalance Indicator prices may be published in increments of $0.025.

Q: What will happen to my GTC order that was placed prior to October 3^rd in a Pilot Stock that was priced in impermissible tick increments?
A: Interactive Brokers will adjust outstanding limit and stop GTC orders in Pilot stocks in Test Groups that are not in permissible tick increments (e.g., a buy limit order at $5.01 will be adjusted to $5.00 and a sell limit at $5.01 adjusted to $5.05).

Q: What will happen to my GTC order placed after October 3^rd that was placed and accepted in a nickel tick increment but the Pilot Stock moves from a Test Group to the Control Group that permits non-nickel increments?
A: The GTC order will automatically be able to be revised by the user in non-nickel increments on the date the Pilot stock moves from the Test Group to the Control Group. Similarly, if a stock is added to Test Group due to a corporate action, IBKR will cancel the GTC order if it is priced in impermissible increments.

Q: Where can I find out more information?

A: See KB2752 or the FINRA website for additional details regarding the Pilot Program: http://www.finra.org/industry/tick-size-pilot-program

How to fix the error: "Library dbcapi.dll cannot be loaded"

Background:

TWS users may receive the following error message upon configuring TWS to use the eSignal data feed:

This error may appear for the following reasons:

Issue A - You are not using the 32 bit version of TWS and/or eSignal:

The 32-bit versions of both TWS and eSignal have to be installed for the integration to work. In the section below you will find the instructions for installing the 32-bit TWS. Should you need assistance with the installation of the 32-bit eSignal, we suggest you to contact the eSignal customer support.

Issue B - There is an incompatibility with the file C:\Jts\dbcapi.dll:

To use 32-bit eSignal version 12, an incompatibility with the C:\Jts\dbcapi.dll file must be fixed. This involves copying a file from the eSignal installation and renaming it to dbcapi.dll.

Note: On certain systems you will need to apply the fixes for both issue A and B. If you applied the fix for issue A (or if you are already sure you are using the 32 bit version of both platforms) and you are still receiving the error message, then please apply as well the fix for issue B.

Instructions to resolve issue A

Installing 32-bit TWS

Please open the page http://www.ibkr.com in your browser and perform the steps below:

1) Click on the Log In button at the top right corner of the page.

2) Click on Download Trader Workstation:

3) Click on the red button TWS Latest:

4) On the next page, click on the link Download for Other Operating Systems:

5) Click on the item Windows 32-bit:

6) Make sure that the description under the DOWNLOAD button has changed to "Windows: 32 bit". Click now on DOWNLOAD:

7) Launch the downloaded file. The Trader Workstation installation will start. At this point, you may see the warning message "Trader Workstation latest is already installed...". Ignore this warning and click on the button Next > to continue the installation:

8) Your "Trader Workstation" Desktop icon will be automatically updated. You can now launch the 32-bit Trader Workstation by a double click on that icon.

If you have launched the 32-bit TWS and the 32 bit version of eSignal but you still receive the same error message, please follow as well the instructions below.

Instructions to resolve issue B

Replacing dbcapi.dll for compatibility between 32-bit TWS and 32-bit eSignal 12

To correct an incompatibility with the dbcapi.dll file, we will replace that file with another version of it taken from the eSignal installation folder. Please follow the steps below to perform the substitution:

1) Navigate to C:\Jts and rename the file dbcapi.dll to dbcapi_old.dll

2) Navigate to the directory where 32-bit eSignal 12 is installed (most commonly C:\Program Files (x86)\Common Files\Interactive Data\DM).

3) Copy dbcapi_vc8.dll from that directory into the C:\Jts directory.

4) Move to the C:\Jts directory.

5) Right click on the dbcapi_vc8.dll file (now in the C:\Jts directory) and select rename. Type dbcapi.dll as the new filename.

6) TWS is now ready to accept the eSignal data feed.

How to install the TWS API Components on Mac / Unix

NOTE: If you have already agreed to the API License Agreement please start at Step 3 below.

Instructions

Click directly on the button below to access the API software download page
This will direct you to Interactive Brokers API License Agreement, please review it
Once you have clicked "I Agree", refer to the Mac / Unix section to download the API Software version of your preference

This will download twsapi_macunix.n.m.zip to your computer
(where n and m are the major and minor version numbers respectively)
Open Terminal (Ctrl+Alt+T on most distributions)
(On Mac press Command+Space to launch Spotlight, then type terminal and press Return)
Navigate to the directory where the installer has been downloaded (normally it should be the Download folder within your home folder) and confirm the file is present

$ cd ~/Downloads
$ ls

Unzip the contents the installer into your home folder with the following command (if prompted, enter your password):
$ sudo unzip twsapi_macunix.n.m.zip -d $HOME/
To access the sample and source files, navigate to the IBJts directory and confirm the subfolders samples and source are present
$ cd ~/IBJts
$ ls

Legacy Instructions - API Version ≤ 9.71

Note: IB only offers API Version 9.72+. In the event you already have an existing legacy version and need to install it, please refer to the directions below:

locate the file twsapi_macunix.n.m.jar on your computer
(where n and m are the major and minor version numbers respectively.)
Open Terminal (Ctrl+Alt+T on most distributions)
(On Mac press Command+Space to launch Spotlight, then type terminal and press Return)
Navigate to the directory where the .jar file has been located (normally it should be the Download folder within your home folder) and confirm it is present
$ cd ~/Downloads
$ ls
Extract the contents of the .jar file into your home folder
$ jar xf twsapi_macunix.n.m.jar -d $ HOME/
To access the sample and source files, navigate to the IBJts directory and confirm the subfolders samples and source are present
$ cd ~/IBJts
$ ls

How to fix the error: "Ddedll.dll file missing or out of date"

Background:

TWS users running add-on applications in Excel using DDE on a Windows 64-bit operating systems may receive the following error message upon log in or when enabling the DDE client:

This message is usually displayed for the following reasons:

Issue A - You are not using the 32-bit version of TWS

You are running an instance of TWS that is using the 64-bit version of the Java Virtual Machine while attempting to load the ddedll.dll library, which has been compiled for 32-bit Java. This error can be corrected by re-installing TWS 32-bit from IB website.

Issue B - The API components have not been installed

The API Components (and consequently the library ddedll.dll) have not yet been installed but you already enabled the DDE Client Connection for TWS. This error can be corrected by installing the API Components.

Note: On certain systems you will need to apply the fixes for both issue A and B. If you applied the fix for issue A (or if you are already sure you are using the 32 bit version of the TWS) and you are still receiving the error message, then please apply as well the fix for issue B.