@Moderator_2 Thanks for replying. Client Code: A51767992

I have observed that the latency for ltp data on websockets is very low (and not variable): about only 20 milliseconds - basically the network delay.

But the latency for L2 data (market depth) is very variable and high too (Anywhere from 100 ms to 2 seconds and even more!). This points that the exchange L2 data is being processed (maybe parsed or other checks, and then sent).

Can a websocket endpoint be added through which the exchange data packet is relayed as it is, so that we can parse it at our end and the data received is faster too?

(If you guys are doing packet reading at your end, the data packet can be broadcasted first (as it is) and then read at your end)

This is a feature request that I really look forward to, I request you to add this if possible!

Your websockets are not relaying data for NSE scrips since 11:20 AM (19 July 2024). Resolve this ASAP. This is ridiculous!

1. In historical data API, I want data from 2014. But I can only retrieve the data from 2017 onwards. Is there a way I can get the data for older dates too?
2. Is the data reliable? Are there missing dates in the data?
3. Which exchanges and instruments are available in historical API?
4. How to get the historical data for older (expired) futures? What are the token numbers for those?

@trader_noob @Moderator_1 @Moderator_2 @admin Can you please look into this? I had been using this for more than 3 months and suddenly it stopped working. This happening in live market hours and then absolutely no support is extremely unprofessional. I had been using Angel One due to the seemingly great support I had received till now but I am extremely disappointed today. I have basically missed today's trading session due to this. I request you to look into this as soon as possible.

@Moderator_2 thanks, its working now. Would request you to implement measures so that this issue doesn't recur.

@trader_noob @Moderator_1 @Moderator_2 @Moderator_3

@trader_noob @admin

@trader_noob Resolved now

Kindly rectify the issue, the websocket is suddenly disconnected.

1. Will the old endpoints ever be removed? If yes, when? (Estimated if not fixed)
2. Are there any benefits in using the new url?

@Moderator_1 Thanks for the response. MCX is still not working though.

@Mastermind Nope, seems like API servers are still not restarted

Your websockets are not relaying data for NSE scrips since 11:20 AM (19 July 2024). Resolve this ASAP. This is ridiculous!

I am connected to the websocket for data, but I have observed a weird issue that has started today only:
Every 25 seconds or so, the websocket gets stuck and takes some delay to release the incoming data. Basically, the latency (local_time - exchange_time) suddenly spikes every 25 seconds.

This has to be some server issue at your end, please check this and sort. As I said, this has started happening from today only.

@Moderator_2 Okay, seems like the issue is situational. The issue at my end occurs specifically in the opening 15 minutes. After that, throughout the day there are no issues. Seems like a server load issue if its only occuring in the opening 15 minutes, right? (The data stops coming and/or latency is too high)