Feature Request : Bracket order

[quant321]

There is no option for placing bracket order in fyers for FNO segment /EQ .

[marketcalls]

Bracker Order, Cover Order, GTT Order are planned in upcoming phases.
It is already part of 2025 roadmap https://www.openalgo.in/roadmap

[quant321]

let me know in which file i can make the changes for bracket order or any other feature for myself . thanks

…

On Fri, Jan 10, 2025 at 3:03 PM Marketcalls ***@***.***> wrote: Bracker Order, Cover Order, GTT Order are planned in upcoming phases. It is already part of 2025 roadmap https://www.openalgo.in/roadmap — Reply to this email directly, view it on GitHub <#180 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKRGUPAYIHOP2LBZGY7BB2L2J6HWLAVCNFSM6AAAAABU52XYOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBSGE4DCOJVGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[marketcalls]

you have to api in restx_api and related broker function in brokers/api/order_api.py where all the order related api is kept

[quant321]

Pls. let me know can we use OpenAlgo for HFT or below 250ms interval .As i can see most of the broker maintained api response below 200ms . Using redit, zeromq, pydantic ,deque, numba or whatever we have in out python aresenal , for faster execution . Also when in future OpenAlgo empowered with websocket data , i guess we can achieve the HFT latency framework ,if not nano but definitely in ms . Kindly share ur thoughts and understanding , and how i can achieve the same .Instead of starting from scratch .

…

On Fri, Jan 10, 2025 at 5:33 PM Marketcalls ***@***.***> wrote: you have to api in restx_api and related broker function in brokers/api/order_api.py where all the order related api is kept — Reply to this email directly, view it on GitHub <#180 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKRGUPALHN6I6T2VGX642JL2J6ZHVAVCNFSM6AAAAABU52XYOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBSGU2DOOJWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>