#
#
6. Adding Connections

This section describes the exchanges/brokers and markets supported by the robot, along with all parameters used when creating each connection. Some connection parameters directly correspond to fields in the exchange's API; for such parameters, we aim to use names that match those in the exchange API. For example: Credentials, SenderCompID, ComplianceID , and many others. Please note that not all parameters specified during trade connection setup are used during authentication. Some parameters — for instance, Trading account(s) - may only be applied when placing or canceling an order. Therefore, successful authentication and bringing a trade connection online do not guarantee that all connection settings are correct. To verify the correctness of all parameters, create a portfolio with one instrument, place an order (e.g., using the clicker) in such a way that it does not immediately execute as a trade (for example, by setting a negative value for the k parameter), and then cancel this order (e.g., via Hard stop.

#
#
6.1. MOEX FORTS

#
#
6.1.1. TWIME и FIFO TWIME

The robot supports connections via the TWIME protocol in both standard TWIME and FIFO TWIME modes. However, using FIFO TWIME requires additional network infrastructure. If you plan to use FIFO TWIME, please notify support in advance. They will deploy the robot on a server where infrastructure-level access to FIFO TWIME is available.

When creating the connection, the choice between TWIME and FIFO TWIME is made by selecting the appropriate TWIME server address.

When ordering this type of connection, keep in mind that two logins at 30 transactions/sec perform better than one login at 60 transactions/sec (see Round robin).

#
#
6.1.1.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to navigate in the list of trade connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.1.1.2. TWIME server

The TWIME server address of the exchange to which the connection will be established. The list includes addresses for both TWIME and FIFO TWIME.

#
#
6.1.1.3. Credentials

Credentials are provided by the broker.

#
#
6.1.1.4. Trading account(s)

Trading account, provided by the broker. It can also be viewed in the terminal (if there are multiple accounts, they should be listed separated by commas):

Alt text

#
#
6.1.1.5. Comment

A unique identifier for all orders within this connection, set by the user for their own convenience. It is an integer ranging from 0 to 1073741823. If not used, leave it as 0.

#
#
6.1.1.6. Round robin

Enabled by default. For improved performance, you can use multiple TWIME connections with the same Trading account(s). When ordering a TWIME connection, keep in mind that two logins at 30 transactions/sec to the same trading account in Round robin mode will perform better than a single login at 60 transactions/sec. In this mode, the robot will send orders to the multiple logins in a round-robin fashion.

#
#
6.1.1.7. ComplianceID

A label for the order creation method used for orders placed through this connection. If no instructions have been provided by the exchange or broker regarding the value of this field, it is recommended to keep the default value.

#
#
6.1.1.8. Max trans

Transactions per second limit. The user's application specifies login performance, where one unit equals 30 transactions per second.

#
#
6.1.1.9. Reserved trans

Default is 0. The number of transactions per second reserved for cancellation orders. Using this parameter reduces the number of order submissions available per second defined by Max trans, but increases the likelihood that the robot will be able to cancel an order in time when prices move.

#
#
6.1.1.10. Move order

Allowed by default. Allows or prohibits the use of order modification (move) commands for this connection.

#
#
6.1.1.11. Fast aggregation mode (on SIMBA)

When this flag is used, the connection will utilize trade data from the market-data connection, specifically from the Orderlog stream of the corresponding SIMBA connection, provided that this stream is in the Enabled state. When this flag is used, the connection will utilize trade data from the market-data connection, specifically from the Orderlog stream of the corresponding SIMBA connection, provided that this stream is in the Deals for today and Deals history widgets, such trades will be displayed with the Aggregated flag.

#
#
6.1.1.12. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement with the broker.

#
#
6.1.2. FAST (FIX Adapted for STreaming)

This connection consists of 4 streams. This is designed to separate rarely used options, as well as to distinguish the resource-intensive but fast Orderlog stream from the slightly slower but lighter Best prices stream.

#
#
6.1.2.1. Futures Definitions

Instrument definition stream for futures. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.1.2.2. Best prices

Best prices stream. Not mandatory. Automatically disabled when the Orderlog stream is set to Enable, as the exchange does not support combining streams on the FAST derivatives market.

#
#
6.1.2.3. Orderlog

Stream of all orders; the aggregated order book is built based on this data. Note that since the order book for a single instrument is constructed using only order data for that specific instrument, levels reconstructed from other instruments' order books (synthetic liquidity) will be missing in such an order book.

#
#
6.1.2.4. Options definitions

Instrument definition stream for options. To trade options, this stream must be set to Enable status.

#
#
6.1.3. SIMBA

This connection consists of 3 streams. This is designed to separate rarely used options.

#
#
6.1.3.1. Futures Definitions

Instrument definition stream for futures. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.1.3.2. Orderlog

Stream of all orders; the aggregated order book is built based on this data. Note that since the order book for a single instrument is constructed using only order data for that specific instrument, levels reconstructed from other instruments' order books (synthetic liquidity) will be missing in such an order book.

#
#
6.1.3.3. Options Definitions

Instrument definition stream for options. To trade options, this stream must be set to Enable status.

#
#
6.2. MOEX Spot

#
#
6.2.1. FIX (Financial Information eXchange)

When connecting to the cash market, we recommend ordering 3 (three) logins for a single trading account, as there are 3 (three) FIX servers on the cash market, and occasionally one or two may become unavailable. This increases the fault tolerance of your trading see. Round robin.

#
#
6.2.1.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.2.1.2. Server

The address of the exchange's FIX server to which the connection will be established.

#
#
6.2.1.3. SenderCompID

The value of this parameter is provided by the broker.

#
#
6.2.1.4. Password

Important: when creating a new connection, if the password does not meet certain criteria, the robot may automatically change the password. Information about password changes can be found in the robot's log. The current connection password can be viewed in the Trade connections widget when editing the connection: Trade connections settings (gear icon)-> Actions->Edit.

For transactional connections to the equity and currency markets of Moscow Exchange, the robot automatically changes the password no more than once per month. Notification about password change can be found in the robot's log.

#
#
6.2.1.5. Trading account(s)

The trading account, provided by the broker. It can also be viewed in the trading terminal (if there are multiple accounts, they should be listed separated by commas):

Alt text

#
#
6.2.1.6. Round robin

Enabled by default. For fault tolerance, we recommend using three FIX connections to the cash market with the same Trading account(s). In Round robin mode, the robot will use them sequentially, so an unexpected disconnection of one of the exchange's FIX servers will not stop trading.

#
#
6.2.1.7. Client code

The client code can be viewed in the terminal linked to the account (press F7 and open the "Money positions" table) or requested from the broker:

Alt text

#
#
6.2.1.8. ComplianceID

A label for the order creation method used for orders placed through this connection. If no instructions have been provided by the exchange or broker regarding the value of this field, it is recommended to keep the default value.

#
#
6.2.1.9. Firm level account

A checked checkbox indicates that the client's account is a firm-level account.

#
#
6.2.1.10. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement with the broker.

#
#
6.2.2. TWIME и FIFO TWIME

TWIME is a binary protocol, a faster alternative to the FIX protocol. The robot supports connections via the TWIME protocol in both TWIME and FIFO TWIME variants. However, using FIFO TWIME requires additional network infrastructure, so if you plan to use FIFO TWIME, please notify support staff in advance—they will place the robot on a server where such connectivity is supported at the infrastructure level. When creating a connection, the choice between TWIME and FIFO TWIME is made by selecting the appropriate TWIME server address to connect to.

#
#
6.2.2.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.2.2.2. TWIME server

The address of the exchange's TWIME server to which the connection will be established. The list includes addresses for both TWIME and FIFO TWIME.

#
#
6.2.2.3. Username

The value of this parameter is provided by the broker.

#
#
6.2.2.4. Password

Important: when creating a new connection, if the password does not meet certain criteria, the robot may automatically change the password. Information about the password change can be found in the robot's log. The current connection password can be viewed in the Trade connections widget when editing the connection: Trade connections settings (gear icon)-> Actions->Edit.

For transactional connections to the equity and currency markets of Moscow Exchange, the robot automatically changes the password no more than once per month. Notification about password change can be found in the robot's log.

#
#
6.2.2.5. Trading account(s)

The trading account, provided by the broker. It can also be viewed in the terminal (if there are multiple accounts, they are listed separated by commas):

Alt text

#
#
6.2.2.6. Round robin

Enabled by default. To improve performance, you can use multiple TWIME connections with the same Trading account(s). In this mode, the robot will send orders to multiple logins in a round-robin fashion.

#
#
6.2.2.7. Client code

The client code can be viewed in the terminal linked to the account (press F7 and open the "Money positions" table) or requested from the broker:

Alt text

#
#
6.2.2.8. Brokerref

The value of this parameter is provided by the broker.

#
#
6.2.2.9. ComplianceID

A label for the order creation method used for orders placed through this connection. If no instructions have been provided by the exchange or broker regarding the value of this field, it is recommended to keep the default value.

#
#
6.2.2.10. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement with the broker.

#
#
6.2.3. FAST

This connection consists of 3 streams. This is designed to separate the Orderlog stream from the Best prices stream. They have similar speed, and the exchange allows their simultaneous use, so they can be enabled together. However, Best prices is clearly less resource-intensive.

#
#
6.2.3.1. Definitions

Instrument definition stream. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.2.3.2. Best prices

Best prices stream. We recommend enabling it simultaneously with the Orderlog stream.

#
#
6.2.3.3. Orderlog

Stream of all orders. We recommend enabling it simultaneously with the Best prices stream.

#
#
6.2.4. SIMBA

This connection consists of 2 streams.

#
#
6.2.4.1. Definitions

Instrument definition stream. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.2.4.2. Orderlog

Stream of all orders; the aggregated order book is built based on this data.

#
#
6.3. MOEX Currency

#
#
6.3.1. FIX

When connecting to the currency market, we recommend ordering 5 (five) logins for a single trading account, as there are 5 (five) FIX servers on the currency market, and occasionally one or two may become unavailable. This increases the fault tolerance of your trading (see. Round robin).

#
#
6.3.1.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.3.1.2. Server

The address of the exchange's FIX server to which the connection will be established. For improved fault tolerance, different addresses should be selected.

#
#
6.3.1.3. SenderCompID

The value of this parameter is provided by the broker.

#
#
6.3.1.4. Password

Password for this FIX connection. If not changed, use the default one shown in the input field.

Important: when creating a new connection, if the password does not meet certain criteria, the robot may automatically change the password. Information about the password change can be found in the robot's log. The current connection password can be viewed in the Trade connections widget when editing the connection: Trade connections settings (gear icon)-> Actions->Edit.

For transactional connections to the equity and currency markets of Moscow Exchange, the robot automatically changes the password no more than once per month. Notification about password change can be found in the robot's log.

#
#
6.3.1.5. Trading account(s)

The trading account, provided by the broker; it can also be viewed in the terminal. If there are multiple accounts, they should be listed separated by commas.

Alt text

#
#
6.3.1.6. Round robin

Enables or disables Round robin'for this connection. For fault tolerance, we recommend using 5 (five) FIX connections to the currency market with the same Trading account(s). In Round robin mode, the robot will use them sequentially, so an unexpected disconnection of one of the exchange's FIX servers will not stop trading.

#
#
6.3.1.7. Client code

The client code can be viewed in the terminal linked to the account (press F7 and open the "Money positions" table) or requested from the broker. When entering, add two slashes '//' at the end. Depending on broker instructions, it might be one slash at the end and one in the middle. If no instructions were given, leave two at the end.

Alt text

#
#
6.3.1.8. ComplianceID

A label for the order creation method used for orders placed through this connection. If no instructions have been provided by the exchange or broker regarding the value of this field, it is recommended to keep the default value.

#
#
6.3.1.9. Firm level account

Indicates that the user's account is a firm-level account. Brokers usually do not know the account level, so it often needs to be determined manually.

#
#
6.3.1.10. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement with the broker.

#
#
6.3.2. TWIME и FIFO TWIME

TWIME is a binary protocol, a faster alternative to the FIX protocol. The robot supports connections via the TWIME protocol in both TWIME and FIFO TWIME variants. However, using FIFO TWIME requires additional network infrastructure, so if you plan to use FIFO TWIME, please notify support staff in advance—they will place the robot on a server where such connectivity is supported at the infrastructure level. When creating a connection, the choice between TWIME and FIFO TWIME is made by selecting the appropriate TWIME server address to conncet to.

#
#
6.3.2.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.3.2.2. TWIME server

The address of the exchange's TWIME server to which the connection will be established. The list includes addresses for both TWIME and FIFO TWIME.

#
#
6.3.2.3. Username

The value of this parameter is provided by the broker.

#
#
6.3.2.4. Password

Important: when creating a new connection, if the password does not meet certain criteria, the robot may automatically change the password. Information about the password change can be found in the robot's log. The current connection password can be viewed in the Trade connections widget when editing the connection: Trade connections settings (gear icon)-> Actions->Edit.

For transactional connections to the equity and currency markets of Moscow Exchange, the robot automatically changes the password no more than once per month. Notification about password change can be found in the robot's log.

#
#
6.3.2.5. Trading account(s)

The trading account, provided by the broker. It can also be viewed in the terminal (if there are multiple accounts, they are listed separated by commas):

Alt text

#
#
6.3.2.6. Round robin

Enabled by default. To improve performance, you can use multiple TWIME connections with the same Trading account(s). In this mode, the robot will send orders to multiple logins in a round-robin fashion.

#
#
6.3.2.7. Client code

The client code can be viewed in the terminal linked to the account (press F7 and open the "Money positions" table) or requested from the broker:

Alt text

#
#
6.3.2.8. Brokerref

The value of this parameter is provided by the broker.

#
#
6.3.2.9. ComplianceID

A label for the order creation method used for orders placed through this connection. If no instructions have been provided by the exchange or broker regarding the value of this field, it is recommended to keep the default value.

#
#
6.3.2.10. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement with the broker.

#
#
6.3.3. FAST

This connection consists of 3 streams. This is designed to separate the Orderlog stream from the Best prices stream. They have similar speed, and the exchange allows their simultaneous use, so they can be enabled together. However, Best prices is clearly less resource-intensive.

#
#
6.3.3.1. Definitions

Instrument definition stream. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.3.3.2. Best prices

Best prices stream. We recommend enabling it simultaneously with the Orderlog stream.

#
#
6.3.3.3. Orderlog

Stream of all orders. We recommend enabling it simultaneously with the Best prices stream.

#
#
6.3.4. FAST Indexes

To view and add indices to the portfolio, this stream must be set to Enable status.

#
#
6.3.5. SIMBA

This connection consists of 2 streams.

#
#
6.3.5.1. Definitions

Instrument definition stream. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.3.5.2. Orderlog

Stream of all orders; the aggregated order book is built based on this data.

#
#
6.4. SPB

#
#
6.4.1. Market Data (Binary Protocol)

The market data connection consists of several data streams. You can activate only the streams you need and disable the unnecessary ones. If an instrument's name starts with SPB_MM_, it represents SPB liquidity only (orders and trades directly from SPB Exchange). If the name starts with SPB_AGGR_, it represents aggregated liquidity from multiple exchanges. If you are a market maker, you most likely have access only to SPB liquidity.

#
#
6.4.1.1. Definitions

Instrument definition stream. To ensure proper operation of the connection, this stream must be set to Enable status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.4.1.2. Commons

Stream of statistical market parameters. Not used within the robot's algorithm, but available via the C++ interface.

#
#
6.4.1.3. Top of book

Best bid and ask prices stream. We recommend NOT enabling it simultaneously with the Orderbook stream.

#
#
6.4.1.4. Orderbook

Order book stream. We recommend NOT enabling it simultaneously with the Top of book stream.

#
#
6.4.2. Binary Protocol Transaction Gateway

Make sure you ordered a binary, not a FIX login. Only one active connection is allowed per login.

#
#
6.4.2.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.4.2.2. Connection type

Direct — a regular connection that connects directly to the exchange. Proxy — used to enable multiple robots to trade through a single connection.

#
#
6.4.2.3. Login

Login for accessing the exchange, taken from the exchange agreement.

#
#
6.4.2.4. Password

Password for accessing the exchange, taken from the exchange agreement.

#
#
6.4.2.5. Trading account(s)

Trading account, taken from the exchange agreement. Multiple accounts can be added, separated by commas.

#
#
6.4.2.6. Member ID

Participant identifier; defaults to 0. If this value does not work, clarify with the exchange.

#
#
6.4.2.7. Client ID

Client code identifier, taken from the exchange agreement.

#
#
6.4.2.8. Market ID

Liquidity pool identifier. Valid values: 0 (liquidity is automatically determined by financial instrument), 1000 (for addressed instruments, SPB Exchange liquidity only), and 1001 (for anonymous instruments, aggregated liquidity).

#
#
6.4.2.9. Comment

Client comment for orders.

#
#
6.4.2.10. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement.

#
#
6.4.3. Proxy connection to the transactional gateway using binary protocol

Used when multiple robots need to trade through the same transactional connection (i.e., under a single login). Configured by support staff using parameters provided by the user. Parameters are the same as for Binary Trading connection.

#
#
6.4.3.1. Name

This value must match the name of the shared memory segment used for message exchange. Clarify with support service.

#
#
6.5. ALOR OPEN API MOEX

#
#
6.5.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.5.2. Refresh token

Token for API access.

#
#
6.5.3. Trading account(s)

Client's trading account

#
#
6.6. ALOR OPEN API SPB

#
#
6.6.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.6.2. Refresh token

Token for API access.

#
#
6.6.3. Trading account(s)

Client's trading account

#
#
6.7. EXANTE

The robot supports only FIX connections to the EXANTE broker. When adding a transactional connection, two FIX connections are created: market data and transactional. Such a pair of connections can be activated or deactivated only together; that is, attempting to deactivate the market data connection will also deactivate the corresponding transactional connection, and vice versa. Since EXANTE broker can provide market data from a large number of exchanges, the Exchange filter field—specifying the list of required exchanges—is mandatory. It is strongly recommended to include only those exchanges whose instruments you actually plan to use.

#
#
6.7.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.7.2. Conn type

Selects the server to which the connection will be established. All servers are identical in terms of protocol and provided information. The difference lies only in their geographical location.

#
#
6.7.3. SenderCompID (trade)

Unique client identifier for the transactional connection, provided by the broker.

#
#
6.7.4. Password (trade)

Password for the transactional connection, provided by the broker. If the broker provided only one password, then most likely the market data and transactional connection passwords are the same.

#
#
6.7.5. Trading account(s)

Client account identifier, obtained from the broker. Multiple accounts can be added, separated by commas.

#
#
6.7.6. Max trans

One of the flood protection system parameters. To avoid triggering the broker's flood control, we count outgoing messages internally. This parameter defines the maximum number of messages allowed within a time interval. If the number of messages sent within the time interval defined by Max trans interval exceeds this value, the robot stops sending messages to the broker.

#
#
6.7.7. Max trans interval

One of the flood protection system parameters. To avoid triggering the broker's flood control, we count outgoing messages internally. This parameter defines the time interval. If the number of messages sent within this interval exceeds the value set in Max trans, the robot stops sending messages to the broker.

#
#
6.7.8. Transactions reserved

One of the flood protection system parameters. This parameter specifies how many transactions per time interval Max trans interval are reserved for order cancellations.That means, even if order submissions hit the robot’s internal flood control limit, the robot will still be able to send cancellation requests up to the number specified in Transactions reserved.

#
#
6.7.9. SenderCompID (feed)

Unique client identifier for the market data connection, provided by the broker.

#
#
6.7.10. Password (feed)

Password for the market data connection, provided by the broker. If the broker provided only one password, then most likely the market data and transactional connection passwords are the same.

#
#
6.7.11. Exchange filter

List of exchanges (separated by commas) from which market data will be received. At least one exchange must be specified. Currently, data is known to be available from the following markets:
a3ecs, absv, adc, af, ai, aicf, aig, aix, altimaam, am1, amex, apis, arca, arg, argo, asc, ascg, asn, asx, asyl, ath, aud, audc, avm, avtf, bats, bist, blackbox, bm, bmf, bmi, bostonzechiel, btm, c.index, cad, carf, cboe, cbot, ccf, chf, cme, comex, courant, cpf, cpm, dam, dcm, diadema, diamageca, dim, dml, dnci, dominion, dsl, e, eam, ec, egam, emea, enam, esplanade, eur, eurex, euronext, exante, fiscoam, forts, fqf, fqifl, fwb, gbp, geist, gk, ham, hkex, htf, ice, inc, index, ipo, iq69, iqsf, jordancap, jse, kgrcap, kif, ky, laif, lat, lcm, lgml, libor, liffe, llcp, lme, lse, lseaim, lseiob, lux, lvam, micex, mifm, mil, moex.tom, mpi, mse, mtg, muskokacap, nasdaq, ncc, ncl, nf, niton, nnps, nomx, ns, nse, nymex, nyse, nzx, oameur, oamusd, oe, oef, oic, omxc, omxh, ose, otcbb, otcmkts, paf, pils, pl, pse, pvb, quan, rig, rub, sb, sek, sgx, sicav, six, smn, somx, ssh, tase, tmx, tocom, tse, tsf, uah, us, uscorp, usd, vse, wcf, wse, xetra, xpira.

#
#
6.7.12. Bind IP

To obtain the correct IP address, please contact support. The address entered in this field should not be provided to the exchange as a server address.

#
#
6.8. CQG

The robot supports only transactional FIX connections to the CQG broker. The CQG transactional connection can operate either in conjunction with an EXANTE market data connection or independently. Since ticker names differ between EXANTE and CQG, when adding a CQG connection that uses EXANTE market data, you must fill in the ticker name mapping dictionary Securities dictionary, adding all instruments you plan to use. When using CQG market data independently, required tickers are added via the Security manager, functionality located in the Data connections widget.

#
#
6.8.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.8.2. Server

Selects the server to which the connection will be established. All servers are identical in terms of protocol and provided information. The difference lies only in their geographical location.

#
#
6.8.3. SenderCompID

Unique client identifier, provided by the broker.

#
#
6.8.4. Password

Password for the connection, provided by the broker.

#
#
6.8.5. SenderSubID

Additional connection identifier. Should remain at its default value unless another value is provided by the broker.

#
#
6.8.6. Client code

Client code, provided by the broker.

#
#
6.8.7. Securities dictionary

Dictionary mapping ticker names in the format EXANTE:CQG. Must be filled in according to the given example.

#
#
6.8.8. Add market-data connection

A checkbox must be checked. If you have your own (non-shared) EXANTE connection, do not check this box.

#
#
6.8.9. Market-data key

This parameter appears after checking the Add market-data connection box.

#
#
6.8.10. Bind IP

To obtain the correct IP address, please contact support. The address entered in this field should not be provided to the exchange as a server address.

#
#
6.9. KRAKEN

Connection to the Kraken exchange's Spot market. The robot supports only connections based on Websocket and REST API. Market data connection is activated as described in section 3.1 Setting up connections. Transactional connection parameters are described below.

#
#
6.9.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.9.2. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in the settings under the API section. The following permissions should be enabled for the key: "Query Funds", "Query Open Orders & Trades", "Query Closed Orders & Trades", "Create & Modify Orders", "Cancel/Close Orders", "Access WebSockets API", "Export Data". The key must be new and not used anywhere else previously.

#
#
6.9.3. Secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in the settings under the API section. The following permissions should be enabled for the key: "Query Funds", "Query Open Orders & Trades", "Query Closed Orders & Trades", "Create & Modify Orders", "Cancel/Close Orders", "Access WebSockets API", "Export Data". The key must be new and not used anywhere else previously.

#
#
6.9.4. Cancel on disconnect

A flag that controls automatic order cancellation by the exchange when the connection between the exchange and the robot is lost.

#
#
6.9.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.10. BITFINEX

The robot supports only connections based on Websocket and REST API. The transactional connection uses two distinct API key pairs, which must be different. Market data connection is activated as described in the Settin up connections section. Transactional connection parameters are described below.

#
#
6.10.1. Name

A field for specifying the connection name. This value is set for user convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters _ a-z A-Z 0-9

#
#
6.10.2. Margin account

Indicates that your account is a margin account.

#
#
6.10.3. API key#0

First public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in the settings under the API section. All possible read and write permissions should be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.10.4. API key secret#0

First secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in the settings under the API section. All possible read and write permissions should be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.10.5. API key#1

Second public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in the settings under the API section. All possible read and write permissions should be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.10.6. API key secret#1

Second secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in the settings under the API section. All possible read and write permissions should be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.10.7. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.11. HitBTC

The robot supports only connection to the HitBTC exchange's Spot section via Websocket and REST API. Market data connection is activated as described in the Setting up connection. Transactional connection parameters are described below.

#
#
6.11.1. Name

A field for specifying the connection name. This value is set for user convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters _ a-z A-Z 0-9

#
#
6.11.2. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under the API keys section. The following permissions should be enabled: "Order book, History, Trading balance", "Place/cancel orders", "Payment information". The key must be new and not used anywhere else previously.

#
#
6.11.3. Secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under the API keys section. The following permissions should be enabled: "Order book, History, Trading balance", "Place/cancel orders", "Payment information". The key must be new and not used anywhere else previously.

#
#
6.11.4. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.12. BITMEX

Connection to the BitMEX exchange's futures market. The robot supports only Websocket and REST API connections. The transactional connection uses two distinct API key pairs, which must be different. Market data connection is activated as described in the Setting up connections. Transactional connection parameters are described below.

#
#
6.12.1. Name

A field for specifying the connection name. This value is set for user convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters _ a-z A-Z 0-9

#
#
6.12.2. ID#0

First public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in settings under the API Keys section. The "Order" permission must be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.12.3. Secret#0

First secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in settings under the API Keys section. The "Order" permission must be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.12.4. ID#1

Second public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in settings under the API Keys section. The "Order" permission must be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.12.5. Secret#1

Second secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in settings under the API Keys section. The "Order" permission must be enabled for this key. The key must be new and not used anywhere else previously.

#
#
6.12.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.13. BINANCE

Connection to Binance exchange's Spot market in either Spot or Margin mode. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connection. Transactional connection parameters are described below.

#
#
6.13.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.13.2. Account type

Account type selection. Options are CLASSIC and PORTOFLIO MARGIN. Detailed descriptions of these modes can be found on the Binance exchange website.

#
#
6.13.3. Margin account

Indicates that your account is a margin account. If enabling this flag, ensure your API key has the "Enable Margin" permission. This parameter is available only when Account type = PORTOFLIO MARGIN.

#
#
6.13.4. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under API Management. The following permissions should be enabled: "Read Info", "Enable Trading". For margin trading, the "Enable Margin" permission should also be enabled. The key must be new and not used anywhere else previously.

#
#
6.13.5. Secret

First secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under API Management. The following permissions should be enabled: "Read Info", "Enable Trading". For margin trading, the "Enable Margin" permission should also be enabled. The key must be new and not used anywhere else previously.

#
#
6.13.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.14. BINANCEFUT

Connection to Binance exchange's USD-M Futures market. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connection. Transactional connection parameters are described below.

#
#
6.14.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.14.2. Account type

Account type selection. Options are CLASSIC and PORTOFLIO MARGIN. Detailed descriptions of these modes can be found on the Binance exchange website.

#
#
6.14.3. Conn type

Connection type selection. If there are no special arrangements with the exchange for direct connectivity, select REGULAR. If you have such an arrangement, contact support in advance to obtain the server IP address from which trading will occur; then, when creating the connection, choose one of the WHITELIST options.

#
#
6.14.4. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under API Management. The following permissions should be enabled: "Read Info", "Enable Trading" и "Enable Future".

#
#
6.14.5. Secret

First secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under API Management. The following permissions should be enabled: "Read Info", "Enable Trading" и "Enable Future".

#
#
6.14.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.14.7. BINANCEFUT Connection Streams Description

binancefut_listen - full-featured connection with order book.

binancefut_listen_0ms - full-featured connection with order book using 0ms aggregation (since 0ms aggregation is NOT documented, use at your own risk).

binancefut_listen_top - full-featured connection without the order book, providing only best bid and ask prices (top of book) with fast updates.

Important:

  • A "full-featured" connection means that enabling just this single stream is sufficient for the robot to operate properly.
  • It is strongly NOT recommended to enable both top of book and order book streams simultaneously in the same robot, as they are NOT synchronized and may cause various side effects (such as trading based on stale prices — where prices in the top of book stream differ from those in the order book).
  • Note that the above is a recommendation, not a strict prohibition.

#
#
6.15. BINANCECM

Connection to Binance exchange's COIN-M Futures market. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connection. Transactional connection parameters are described below.

#
#
6.15.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.15.2. Account type

Account type selection. Options are CLASSIC and PORTOFLIO MARGIN. Detailed descriptions of these modes can be found on the Binance exchange website.

#
#
6.15.3. Conn type

Connection type selection. If there are no special arrangements with the exchange for direct connectivity, select REGULAR. If you have such an arrangement, contact support in advance to obtain the server IP address from which trading will occur; then, when creating the connection, choose one of the WHITELIST options.

#
#
6.15.4. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under API Management. The following permissions should be enabled: "Read Info", "Enable Trading" and "Enable Future".

#
#
6.15.5. Secret

First secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under API Management. The following permissions should be enabled: "Read Info", "Enable Trading" and "Enable Future".

#
#
6.15.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.15.7. BINANCECM Connection Streams Description

binancecm_listen - full-featured connection with order book.

binancecm_listen_0ms - full-featured connection with order book using 0ms aggregation (since 0ms aggregation is NOT documented, use at your own risk).

binancecm_listen_top - full-featured connection without the order book, providing only best bid and ask prices (top of book) with fast updates.

Important:

  • A "full-featured" connection means that enabling just this single stream is sufficient for the robot to operate properly.
  • It is strongly NOT recommended to enable both top of book and order book streams simultaneously in the same robot, as they are NOT synchronized and may cause various side effects (such as trading based on stale prices — where prices in the top of book stream differ from those in the order book).
  • Note that the above is a recommendation, not a strict prohibition.

#
#
6.16. DERIBIT

The robot supports only Websocket API connections. There are two ways to add a market data connection:

  1. Public market data connection — activated as described in the Setting up connections;
  2. If you are creating a transactional connection, you can set the Create fast data connection flag, In this case, a market data connection will be created using the same credentials as the transactional connection. The market data connection created via the second method will react slightly faster to market changes. Additionally, such a paired connection can only be activated or deactivated together with the transactional connection. Transactional connection parameters are described below.

#
#
6.16.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.16.2. Server

Select between live and test environments. By default, the connection is created to the live environment.

#
#
6.16.3. Access Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under the API section. For this key, set permission "read_write" in the Trade field and "read" for all other fields.

#
#
6.16.4. Access secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under the API section. For this key, set permission "read_write" in the Trade field and "read" for all other fields.

#
#
6.16.5. Create fast data connection

Set this flag if you want to create a fast market data connection using the same key pair as the transactional connection.

#
#
6.16.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.17. OKX

Connection to OKX exchange platforms: SPOT, SWAP, FUTURES, OPTION, in cross, isolated, and cash modes. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.17.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.17.2. Conn type

Select the server to connect to. If you plan to trade from a server hosted on AWS, choose the AMAZON option.

#
#
6.17.3. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under the API section. Permissions for reading and trading must be enabled. The "Order placement mode" field must be set to "Net". The key must be new and not used anywhere else previously.

#
#
6.17.4. Secret Key

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under the API section. Permissions for reading and trading must be enabled. The "Order placement mode" field must be set to "Net". The key must be new and not used anywhere else previously.

#
#
6.17.5. Password

Password for accessing the exchange.

#
#
6.17.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.18. BEQUANT

The robot supports BEQUANT connections via both Websocket/REST API and FIX protocol. Public market data connection via Websocket and REST API is activated as described in the Setting up connections chaper. When creating a transactional connection, you can select which connection type to use. Adding a transactional FIX connection creates two FIX connections: market data and transactional. Such a pair can only be activated or deactivated together — attempting to deactivate the market data connection will also deactivate the transactional one, and vice versa. Transactional connection parameters are described below.

#
#
6.18.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.18.2. Conn type

Connection type. Available options are FIX and WEBSOCKET. The WEBSOCKET connection can use keys generated by the user in the exchange's personal account. The FIX connection requires contacting exchange support to obtain access.

#
#
6.18.2.1. FIX Connection Parameters

The FIX connection requires establishing a VPN connection; therefore, contact support before adding the connection and provide the required VPN parameters.

#
#
6.18.2.1.1. Server

Select the server to connect to. If the required address is not in the list, contact support.

#
#
6.18.2.1.2. Exchange account id

User identifier on the exchange. Can be found in the user’s personal account or requested from exchange support. Enter only the identifier itself, without prefixes such a "login_", "user_" etc.

#
#
6.18.2.1.3. Password

Password for the FIX connection. Provided by the exchange along with other FIX connection parameters.

#
#
6.18.2.2. WEBSOCKET Connection Parameters

#
#
6.18.2.2.1. API

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in account settings under the "API keys" section. The following permissions should be enabled: "Order book, History, Trading balance", "Place/cancel orders", "Payment information". The key must be new and not used anywhere else previously.

#
#
6.18.2.2.2. Secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in account settings under the "API keys" section. The following permissions should be enabled: "Order book, History, Trading balance", "Place/cancel orders", "Payment information". The key must be new and not used anywhere else previously.

#
#
6.18.3. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.19. KRAKENFUT

Connection to Kraken exchange's Futures market. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.19.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.19.2. Conn type

Select the connection type. If there are no special arrangements with the exchange for direct connectivity, choose REGULAR. If you have such an arrangement, contact support in advance to obtain the server IP address from which trading will occur, then select DIRECT when creating the connection.

#
#
6.19.3. API Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located in settings under the API section. Access level must be set to "Full access". The key must be new and not used anywhere else previously.

#
#
6.19.4. Secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located in settings under the API section. Access level must be set to "Full access". The key must be new and not used anywhere else previously.

#
#
6.19.5. Cancel on disconnect

Flag that controls automatic order cancellation by the exchange upon disconnection between the exchange and the robot.

#
#
6.19.6. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.20. KUCOIN

The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.20.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.20.2. Passphrase

Password phrase for accessing the exchange.

#
#
6.20.3. Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.20.4. Secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.20.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.21. HUOBI

Connection to the Spot market of Huobi Global exchange. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.21.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.21.2. Server

Select the server to connect to. If you plan to trade from a server hosted on AWS, choose the option api-aws.huobi.pro

#
#
6.21.3. Access Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.21.4. Secret Key

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.21.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.22. HUOBIFUT

Connection to the Coin-M Futures market of Huobi Global exchange. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connectionschapter. Transactional connection parameters are described below.

#
#
6.22.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.22.2. Server

Select the server to connect to. If you plan to trade from a server hosted on AWS, choose the AMAZON option.

#
#
6.22.3. Access Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.22.4. Secret Key

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.22.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.23. HUOBIFUTCM

Connection to the Coin-M Swaps market of Huobi Global exchange. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connectionschapter. Transactional connection parameters are described below.

#
#
6.23.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.23.2. Server

Select the server to connect to. If you plan to trade from a server hosted on AWS, choose the AMAZON option.

#
#
6.23.3. Access Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.23.4. Secret Key

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.23.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.24. HUOBIFUTUM

Connection to the USDT-M market of Huobi Global exchange. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.24.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.24.2. Server

Select the server to connect to. If you plan to trade from a server hosted on AWS, choose the AMAZON option.

#
#
6.24.3. Access Key

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.24.4. Secret Key

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.24.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.25. VIKINGTRADE

The robot supports only Websocket API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.25.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.25.2. Conn type

Select between live and test environments. By default, the connection is created to the live environment.

#
#
6.25.3. Public key id

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Located under Account → API. When creating the key, trading permission must be enabled.

#
#
6.25.4. Access secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Located under Account → API. When creating the key, trading permission must be enabled.

#
#
6.25.5. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.26. BYBIT

Connection to Bybit exchange markets: Inverse Perpetual, USDT Perpetual, and Inverse Futures. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.26.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.26.2. Public key id

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.26.3. Access secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.26.4. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.27. BYBITSPOT

Connection to Bybit exchange's Spot market. The robot supports only Websocket and REST API connections. Market data connection is activated as described in the Setting up connections chapter. Transactional connection parameters are described below.

#
#
6.27.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9

#
#
6.27.2. Public key id

Public API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding secret key. Usually located under Settings → Security → API.

#
#
6.27.3. Access secret

Secret API key for accessing the exchange API. Created in the user account on the exchange website together with the corresponding public key. Usually located under Settings → Security → API.

#
#
6.27.4. Bind IP

If the agreement does not require connection from a fixed IP address, set the value to Automatic. Otherwise, contact support to confirm the server address. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.28. CTRADER

The robot supports only FIX connections to the cTrader broker. When adding a transactional connection, two FIX connections are created: market data and transactional. Such a pair can be activated or deactivated only together — attempting to deactivate the market data connection will also deactivate the corresponding transactional connection, and vice versa.

#
#
6.28.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.28.2. Conn type

Selects the server to which the connection will be established. All servers are identical in terms of protocol and provided information. The difference lies only in their geographical location.

#
#
6.28.3. SenderCompID

Unique client identifier, provided by the broker.

#
#
6.28.4. Login

cTrader account number.

#
#
6.28.5. Password (trade)

Password for both trading and market data FIX connections; matches the password of the cTrader account.

#
#
6.28.6. Try to use only one position for one instrument

A flag that, when enabled, prevents the robot from placing more than one order per instrument if no open position exists. As soon as this order is executed and an open position is created, all restrictions on placing further orders for that instrument are lifted.

#
#
6.28.7. Bind IP

To obtain the correct IP address, please contact support. The address entered in this field should not be provided to the exchange as a server address.

#
#
6.29. IMEX

#
#
6.29.1. Market Data (binary protocol)

The market data connection consists of several data streams. You can activate only the streams you need and disable the unnecessary ones. If an instrument's name starts with IMEX_MM_, it represents IMEX liquidity only (orders and trades directly from IMEX exchange). If the name starts with IMEX_AGGR_, it represents aggregated liquidity from various exchanges. If the instrument name starts with IMEX_OKX_, it represents liquidity from OKX exchange.

#
#
6.29.1.1. Definitions

Instrument definition stream. To ensure proper operation of the connection, this stream must be set to "Enable" status. In addition to instrument definitions, trading statuses and price limits are also transmitted through this stream.

#
#
6.29.1.2. Top of book

Best bid and ask prices stream. We recommend NOT enabling it simultaneously with the Orderbook stream.

#
#
6.29.1.3. Orderbook

Order book stream. We recommend NOT enabling it simultaneously with the Top of book stream.

#
#
6.29.2. Binary Protocol Transaction Gateway

Make sure you ordered a binary, not a FIX login. Only one active connection is allowed per login.

#
#
6.29.2.1. Name

A field for specifying the connection name. This value is set for convenience, to make it easier to identify the connection within the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.29.2.2. Login

Login for accessing the exchange, taken from the exchange agreement.

#
#
6.29.2.3. Password

Password for accessing the exchange, taken from the exchange agreement.

#
#
6.29.2.4. Trading account(s)

Trading account, taken from the exchange agreement. Multiple accounts can be added, separated by commas.

#
#
6.29.2.5. Member ID

Participant identifier; defaults to 0. If this value does not work, clarify with the exchange.

#
#
6.29.2.6. IMEX comment

Text comment added to every order submitted via this connection.

#
#
6.29.2.7. Client ID

Client code identifier, taken from the exchange agreement.

#
#
6.29.2.8. Market ID

Used for routing orders to the appropriate liquidity pool; the correct value should be clarified with the exchange.

#
#
6.29.2.9. Prime exchange

Used for routing orders to the appropriate liquidity pool; the correct value should be clarified with the exchange.

#
#
6.29.2.10. Comment

Client comment for orders.

#
#
6.29.2.11. Bind IP

The IP address from which the connection to the exchange will be established. The IP address must be specified in the agreement.

#
#
6.30. J2T

The robot supports only FIX connectivity to the broker JUST2TRADE.

#
#
6.30.1. Name

A field for setting the connection name. This value is set for convenience, to make it easier to identify the connection in the list of transactional connections. Allowed characters: _ a-z A-Z 0-9.

#
#
6.30.2. Server

Selects the server to which the connection will be established. Currently, only one server is available.

#
#
6.30.3. SenderCompID

The client's unique identifier, provided by the broker. The broker JUST2TRADE confuses the FIX protocol fields SenderCompID and TargetCompID. Therefore, from the two fields provided by the broker (SenderCompID and TargetCompID), you must use the one whose value is different from J2TT.

#
#
6.30.4. Login

The client account name for JUST2TRADE.

#
#
6.30.5. Password

Password for the trading FIX connection; may be the same as the JUST2TRADE account password.

#
#
6.30.6. Client code

Client code is used when adding order. Most often, the value is a numeric identifier contained in the client`s login. Since the value of this field does not affect connection authentication, you should try adding order to verify that this field is set correctly.

#
#
6.30.7. Use SSL/TLS

A flag indicating whether SSL/TLS encryption should be used. Information about whether encryption is enabled for a given login is provided by the broker.

#
#
6.30.8. Bind IP

To clarify the IP address, please contact support. The address specified in this field should not be provided to the exchange as the server address.

#
#
6.31. SPIMEX

Description is under development

#
#
6.32. LMAX

Description is under development