Please provide current positions and pnl of current position provide through web socket.
I am trying to fetch current positions for every second and trying to check pnl but its getting delayed result and that too data is not consistent sometimes getting empty data of current positions.
To check pnl of current positions needs to check mobile app or website this not good. For next version please provide pnl realized and unrealized pnl and other info through websocket so that no need to check mobile.
Sorry for the trouble - yes weâre aware that the P&L result on REST comes with slightly delayed market data. Weâre working on getting the P&L data on the REST call to reflect with the latest market data. Aiming to get this improvement done by this month.
Instead of REST please update position data with web socket for consist and reliable data.
Dont provide too many parameters as well like buy qty and sell qty as different parameters provide like 50 for buy and -50 for sell because of that getting lot of problems for extracting data and getting required things.
Make api simple as much as possible which can be understood by very beginner as well.
If you want check for fyers v3 they have done very good job in this but due to trust factors i am looking for Upstox.
Make api free for lifetime almost all brokers providing api as free.
I hope you will take this feedback and you will improve this thing.
Just to keep you posted. Not just position update but also holdings update events would be useful. The good news is we already support both of these events in our WebSockets for our platforms so extending to API wonât be super difficult.
What we need to double check are whether it will break existing users of WS and how to handle it gracefully.
Today weâre releasing an update to send all order updates to WebSocket (whether placed on API or not). Following that up with updating the P&L numbers sent on getPositions call to be more recent (instead of 1 min). After that, weâll take this up and find a way to deploy it in a way that it doesnât break existing implementations.
Also - API is and will remain free! What we are promoting right now is zero brokerage on API until end of Feb
Havenât fully scoped it yet to give you a timeline right now. Whatever changes will come through - we are going to see that it doesnât break existing implementations
I have implemented my own logic for fetching Realtime but now facing issue with websocket.
After implementation facing frequent websocket disconnection. Before implementation I was not observed this behaviour.
How to handle this scenario? I am not much expert in python.
I am suspecting because one common variable is updated in web socket code which is async and reading the same variable in thread at the interval of100ms.
Is it correct or any other method can i use for implementation.
