Take profit & stop loss implementation with Limit & Stop orders
- ← Previous
- 1
- 2
- 3 (current)
- Next →
Take profit & stop loss implementation with Limit & Stop orders
PanagiotisCharalampous said:
Hi massimiliano.quarti,
You can use FIX API only for the account that is currently logged in.
Best Regards,
Panagiotis
but the fixapi is working, i open the positions to the different accounts, the think that is not working is the usage of 721 field to make the sl and tp orders working as an an OCO order in hedging accounts.
Hi massimiliano.quarti,
You should not be acle to trade for a different account than the one that is logged in. If this is the case, we will investigate it and fix it.
Best Regards,
Panagiotis
RE:
That is not a good news. How is possible to build a copier without that mechanism?
My client needs a copier between differents accounts, which api i have to use? Openapi has the same modality of working?
PanagiotisCharalampous said:
Hi massimiliano.quarti,
You should not be acle to trade for a different account than the one that is logged in. If this is the case, we will investigate it and fix it.
Best Regards,
Panagiotis
RE: RE:
That is what i'm trying to do. I think that fixapi is made to this usage from every application like you use to do in the samples in github
Hi massimiliano.quarti,
If you need to trade on behalf of somebody else, you need to use Open API.
Best Regards,
Panagiotis
PanagiotisCharalampous said:
Hi massimiliano.quarti,
If you need to trade on behalf of somebody else, you need to use Open API.
Best Regards,
Panagiotis
I am also working a copy trading solution just similar to one described by massimiliano.quarti
My main account under a bot will create a master order, that I would like to copy to possibly thousands of my customer accounts.
How I am thinking to manage it like, designing a copy trading engine as described by massimiliano.quarti using FIX API, where I need to manage three orders first one to manage main trade, second one to manage SL, and third to manage a TP, but you suggested to use Open API instead of FIX API, but probably you know there certain limitations posed on requests per second under one Open API application
so how can I manage possibly 1000s of requests per second using Open API?
RE:
ctid5718405 said:
PanagiotisCharalampous said:
Hi massimiliano.quarti,
If you need to trade on behalf of somebody else, you need to use Open API.
Best Regards,
Panagiotis
I am also working a copy trading solution just similar to one described by massimiliano.quarti
My main account under a bot will create a master order, that I would like to copy to possibly thousands of my customer accounts.
How I am thinking to manage it like, designing a copy trading engine as described by massimiliano.quarti using FIX API, where I need to manage three orders first one to manage main trade, second one to manage SL, and third to manage a TP, but you suggested to use Open API instead of FIX API, but probably you know there certain limitations posed on requests per second under one Open API application
so how can I manage possibly 1000s of requests per second using Open API?
After a lot of research and deliberation, I came up with a solution that can copy trade on behalf of possibly1000s of customers having their ctrader accounts, my solution is based on.
- A serverless and Microsoft Azure cloud-based application (Azure Event Grid, with Azure Functions),
- ctrader Open API
- SQL Server (In memory OLTP)
RE: RE:
Please contact me i'm still searching a valid solution
ctid5718405 said:
ctid5718405 said:
PanagiotisCharalampous said:
Hi massimiliano.quarti,
If you need to trade on behalf of somebody else, you need to use Open API.
Best Regards,
Panagiotis
I am also working a copy trading solution just similar to one described by massimiliano.quarti
My main account under a bot will create a master order, that I would like to copy to possibly thousands of my customer accounts.
How I am thinking to manage it like, designing a copy trading engine as described by massimiliano.quarti using FIX API, where I need to manage three orders first one to manage main trade, second one to manage SL, and third to manage a TP, but you suggested to use Open API instead of FIX API, but probably you know there certain limitations posed on requests per second under one Open API application
so how can I manage possibly 1000s of requests per second using Open API?
After a lot of research and deliberation, I came up with a solution that can copy trade on behalf of possibly1000s of customers having their ctrader accounts, my solution is based on.
- A serverless and Microsoft Azure cloud-based application (Azure Event Grid, with Azure Functions),
- ctrader Open API
- SQL Server (In memory OLTP)
RE: RE: RE:
massimiliano.quarti please provide your contact details
massimiliano.quarti said:
Please contact me i'm still searching a valid solution
ctid5718405 said:
ctid5718405 said:
PanagiotisCharalampous said:
Hi massimiliano.quarti,
If you need to trade on behalf of somebody else, you need to use Open API.
Best Regards,
Panagiotis
I am also working a copy trading solution just similar to one described by massimiliano.quarti
My main account under a bot will create a master order, that I would like to copy to possibly thousands of my customer accounts.
How I am thinking to manage it like, designing a copy trading engine as described by massimiliano.quarti using FIX API, where I need to manage three orders first one to manage main trade, second one to manage SL, and third to manage a TP, but you suggested to use Open API instead of FIX API, but probably you know there certain limitations posed on requests per second under one Open API application
so how can I manage possibly 1000s of requests per second using Open API?
After a lot of research and deliberation, I came up with a solution that can copy trade on behalf of possibly1000s of customers having their ctrader accounts, my solution is based on.
- A serverless and Microsoft Azure cloud-based application (Azure Event Grid, with Azure Functions),
- ctrader Open API
- SQL Server (In memory OLTP)
- ← Previous
- 1
- 2
- 3 (current)
- Next →