dm.skpd
22 Mar 2017, 14:54

RE:

Spotware said:

Hi dm.skpd

Yes this will be updated soon.

Thank you.

dm.skpd
22 Mar 2017, 14:23

Hi Spotware,

Your FIX API credentials page should look like this

There is no host name in web version. It should be updated soon?

dm.skpd
22 Mar 2017, 13:58

RE: RE:

#EOL said:

What hostname are you talking about?

Probably h23.p.ctrader.com, but not sure.

They have changed IP again, but all three still accept connections (same behavior for first IP - can't trade, ok for two new - can trade).

And, probably, you may want to change your password for accounts fxpig.3000369 and fxpig.3000367, since they are exposed in the FIX logs you posted earlier (tag 554)

Not really. These are demo accounts, pasted as is to not confuse with invalid checksum.

dm.skpd
21 Mar 2017, 18:04

RE:

Spotware said:

Hi dm.skpd,

Can you verify that you are sending Trade messages to 5202 and not 5201? 

Right after your message FXPIG changed their connection settings (IP address) and now I can successfully use Logon and NewOrder messages on 5202 port.

That is good part, thank you!

On a side note: nothing was changed for rest brokers, I still can't Logon on 5202 port for brokers: pepperstone, icmarkets, fxpro.

dm.skpd
21 Mar 2017, 15:03

RE:

#EOL said:

You are sending orders to market data connection. Try trade one, it's on the different port and TargetSubID (tag 57) = TRADE

Logon message is rejected on trade connection (5202 port, tag 57 = TRADE):

OUT >>> 8=FIX.4.4|9=114|35=A|34=1|49=fxpig.3000367|52=20170321-12:58:55.024|56=CSERVER|57=TRADE|98=0|108=3|141=Y|553=3000367|554=1mrMZapI|10=247|

IN <<< 8=FIX.4.4|9=151|35=5|34=1|49=CSERVER|50=TRADE|52=20170321-12:58:55.364|56=fxpig.3000367|58=TargetSubID is assigned with the unexpected value 'TRADE', expected 'QUOTE'|10=101|

Same across almost all brokers, except roboforex (which do not offer netting account, so not really suitable).

Does this mean that most of the cTrader's brokers can't handle new orders via FIX API?