Spotware
14 Feb 2017, 10:06

Hi lec0456,

Can we have a more detailed description of what you are doing and why you think there is a problem when testing? It will help us determine if there is a problem or not.

Spotware
13 Feb 2017, 12:10

Hi,

We just wanted to inform you that FIX API with Hedging Support has beer released

http://www.spotware.com/about/news-updates/press-release%3A-ctrader-supports-fix-api-trading-with-hedging-accounts/861

Also we have upoloaded an example application on GitHub on how to send and receive FIX messages to and from cServer. You can find an explanatory article here

https://help.spotware.com/FIX/FIXSample

Let us know if you need any further assistance.

Spotware
13 Feb 2017, 12:05

Hi mindbreaker,

We tried to make the example as simple as possible. If you can explicitely state what kind of example you need (i.e. type of application, programming language) then maybe a community member could help you. 

Spotware
13 Feb 2017, 09:57

Hi iAlchemist,

FIX API can be used to connect and send messages to your broker's cServer. Therefore you can use FIX API only with brokers that offer the cTrader platform.

Spotware
13 Feb 2017, 09:53

Hi mindbreaker,

1) In order to close a position, you need to send a NewOrderSingle request with the reverse direction and the PostionID as a paramater. See below

var message = _messageConstructor.NewOrderSingleMessage(MessageConstructor.SessionQualifier.TRADE, _messageSequenceNumber, "1408471", 1,2, DateTime.UtcNow.ToString("yyyyMMdd-HH:mm:ss"), 1000,1, "1",0,0,"", "438169");
          

2) This is not supported by FIX API. You will need to develop this logic yourself.

3) It is not possible now and we don't think that this is going to be added as it defeats the purpose of FIX, which is to reduce the necessary information transmitted to minimum for performance reasons.

If points 2 and 3 are important for you you might consider using Trading API instead of FIX

Spotware
13 Feb 2017, 09:08

Hi mindbreaker,

You can find a working example here https://github.com/spotware/Connect-API-ASP.Net-Sample. Let us know if you have any specific questions.

Spotware
10 Feb 2017, 18:42

Hello,

To get a more helpful response from the community you may want to provide more details about this scenario. 

Many thanks, 

Spotware
10 Feb 2017, 18:39

Hi GoldnOil750, Thanks for providing more details. We will investigate as part of the similar complaint from justin1. We have already collected some detailed information from brokers about this. We expect that on Monday the issue of trades not being mirrored will be resolved. 

Many thanks and sorry for the slow reply. 

Spotware
10 Feb 2017, 18:34

RE: RE:

galafrin said:

Spotware said:

Hi there,

Thanks for your post in our forum. I am sorry that you find this situation frustrating. 

Allow us to explain and perhaps you may understand and respect our position. We have a team dedicated to support brokers, because we are a B2B company and they are our clients. Our current team can handle up to 100 brokers (100 entities). Our team cannot handle 300,000 traders (300,000 entities). The fees we charge brokers reflect the requirement to support a single entity only, not their thousands upon thousands of clients. 

In a typical supply chain situation we would be considered a wholesaler or even manufacturer. Our fees to brokers are a fraction of what they are to end users, becuase they have large overheads - such as large support teams.

Brokers are responsible for supporting their clients (you) and Spotware (us) are responsible for supporting them. 

PS - we screen calls and have a white list of number who are our clients. 

I hope this explanation is well received. 

Regards,

Spotware Team

Not very diplomatic for those who are at the start of your food chain , hey , some bugs have to be reported out there don't you think , that is if you intend to stick around the  next five years.!

The main point we were trying to express here is, if there is a bug then it should be reported to the broker, then they should collect all of the details and provide Spotware with the information they obtained, or already have on record due to the relationship they have with their client. Then Spotware will investigate. 

Furthermore, if there is a common complaint from several users, then they can all report it to their broker, each broker will make a single complaint to us by collecting the information from all of the users and we will investigate and advise the broker, who will advise the several clients. The broker has the support team to handle this and this one of the reasons why you pay a trading commission to them, for support if something goes wrong or you need some help. 

If Spotware actually tried to provide individual support to all cTrader users, we would not last 5 months, let alone 5 years.

Many thanks,

Spotware
10 Feb 2017, 18:17

RE: RE:

tmc. said:

Spotware said:

Hi there,

Thanks for your post in our forum. I am sorry that you find this situation frustrating. 

Allow us to explain and perhaps you may understand and respect our position. We have a team dedicated to support brokers, because we are a B2B company and they are our clients. Our current team can handle up to 100 brokers (100 entities). Our team cannot handle 300,000 traders (300,000 entities). The fees we charge brokers reflect the requirement to support a single entity only, not their thousands upon thousands of clients. 

In a typical supply chain situation we would be considered a wholesaler or even manufacturer. Our fees to brokers are a fraction of what they are to end users, becuase they have large overheads - such as large support teams.

Brokers are responsible for supporting their clients (you) and Spotware (us) are responsible for supporting them. 

PS - we screen calls and have a white list of number who are our clients. 

I hope this explanation is well received. 

Regards,

Spotware Team

Are you saying that Spotware Team is focused into cBroker development and support only? You should consider changing your signature then, "TRADERS FIRST™ Vote for your favorite features: http://vote.spotware.com/" is little bit outdated (over 3 years already), don't you think?

NO, that is not what we meant. Our main priority remains developing our client side applications (cTrader etc.). cBroker is simply an admin panel and is obviously updated to keep up to date with our trading platform developments. We have a large development team who work to support several products (desktop, web, mobile, cTrader, cAlgo, cMirror etc. etc.), we have a support team who work to support 100 brokers, those 100 brokers work to support all of the users of cTrader. 

The objective is to create a product that traders will want and therefore brokers will need to offer it. 

Hope this clarification makes more sense. The priority of our products remains TRADERS FIRST.

Spotware
10 Feb 2017, 18:02

Dear Trader,

Thank you for reporting this. We will investigate ourselves and update in this thread if we have any questions or updates. 

Many thanks, 

Spotware
10 Feb 2017, 17:56

RE: RE:

moneybiz said:

Spotware said:

All server are connected to real price feeds via FIX API, Spotware also manages those integrations directly with the technology provider who supports them.

It would be impossible for a broker to compromise cServer.

cServer <- Manipulated Price Feeds Server <- LP Price Feeds Server
So you're claiming that there is no possibility for a server in the middle between cServer and liquidity provider's price feeds, because you directly manage this integration?

Spotware is responsible for establishing the connection to the broker’s liquidity provider, we are given credentials and FIX specifications to integrate. We do not integrate with any random companies, only well-known and trusted providers. 

It can take up to one month of development including extensive testing to integrate a new FIX API and we will not waste our time on unknown and unreliable companies, and of course the harm that could be caused to our reputation by this association. 

Hope this is clear. 

Spotware
10 Feb 2017, 17:41

Hello,

The when the application launches wherever you are in the world, whether it's from a VPS in London or your local PC in Australia, the application will search all of the available proxies and test them to determine the best one to use. There is no decission making responsibility for you as a user. 

Hope this is clear. 

Many thanks, 

Spotware
10 Feb 2017, 17:38

Hello,

@GoldnOil750 thanks for reporting it, but what exactly do you mean by "down", because at no point was cMirror unavailable. If there is some specific problem you notice, the details are helpful to understand what steps need to be taken from our side. 

@justin1, thank you for those details. This was helpful for us to start an investigation. We will update you if we find anything specifically regarding the mirroring of Stop Orders. 

Many thanks,

Spotware
08 Feb 2017, 17:15

Hi mindbreaker,

Just seen the code. You are indeed using an older version. Please get the latest one. Also

  private string _senderSubID = "TRADE";

You need to assign your account ID to _senderSubID. Please see latest Rules of Engagement https://www.spotware.com/pdf/cTraderFixApi_v2.9.1.pdf?v2.9.1

Spotware
08 Feb 2017, 17:11

Hi mindbreaker,

Thanks for your post. First of all, please verify that you have the latest version of the code. We fixed a similar issue yesterday. We have just tried the latest version on a demo server locally and works ok.

The FIX API sample has been uploaded recently and has taken into consideration the latest Rules of Engagement which have not been deployed on live servers yet. Full deployment is scheduled over the weekend so we would recommend to have a look at it next week. 

Regarding the error, we aknowledge that the application is not bullet proof so some errors might occur. It serves moslty an educational purpose to demonstrate users how to construct, send and receive a FIX API message. If you need a production ready FIX engine, you will need develop the code sample further.

You can read more here https://help.spotware.com/FIX/FIXSample 

Let us know if your issue is resolved or if it persists after Monday.

Spotware
07 Feb 2017, 10:03

Hi there,

Thanks for your post in our forum. I am sorry that you find this situation frustrating. 

Allow us to explain and perhaps you may understand and respect our position. We have a team dedicated to support brokers, because we are a B2B company and they are our clients. Our current team can handle up to 100 brokers (100 entities). Our team cannot handle 300,000 traders (300,000 entities). The fees we charge brokers reflect the requirement to support a single entity only, not their thousands upon thousands of clients. 

In a typical supply chain situation we would be considered a wholesaler or even manufacturer. Our fees to brokers are a fraction of what they are to end users, becuase they have large overheads - such as large support teams.

Brokers are responsible for supporting their clients (you) and Spotware (us) are responsible for supporting them. 

PS - we screen calls and have a white list of number who are our clients. 

I hope this explanation is well received. 

Regards,

Spotware Team

Spotware
03 Feb 2017, 16:15

Dear Ilya,

Thanks for your message. Proxies are used only for sending messages to the Trading API. https://connect.spotware.com is used for authentication and should always remain the same. The same applies for the Accounts API where you should always use https://api.spotware.com.

Let me know if this solves your issue.

Spotware
30 Jan 2017, 13:29

Hello.

You can vote for Heiken Ashi chart to be added here: http://vote.spotware.com/forums/229166-ideas-and-suggestions-for-ctrader-and-calgo/suggestions/5827682-please-add-heiken-ashi-charts-on-ctrader.

It is already in our plans to include this popular chart type in cTrader for Windows. 

Many thanks.

Spotware
30 Jan 2017, 12:12

Hello.

Each broker has their own cTrader and the account number and login is respective to that. There is not one universal cTrader for all brokers. Sorry you found this process complicated. 

Many thanks.