Is anyone seeing issues with QUOTES API response TRADINGSYMBOL?
-
Hello @admin,
We’ve noticed an issue with the Quotes API today — it’s returning incorrect trading symbols. Specifically, when quoting Futures or Options, it’s only returning the base symbol instead of the full trading symbol.
For example, instead of getting "PNB28OCT25FUT", the API is returning just "PNB".
This functionality was working fine until Friday, so it seems something may have changed or broken over the weekend.
Could you please check and advise?
I am requesting a quote for PNB28OCT25FUT and got below response.
{ "status": true, "message": "SUCCESS", "errorcode": "", "data": { "fetched": [ { "exchange": "NFO", "tradingSymbol": "PNB", "symbolToken": "52500", "ltp": 110.03, "open": 108.94, "high": 110.19, "low": 108.94, "close": 108.56, "lastTradeQty": 8000, "exchFeedTime": "29-Sep-2025 09:57:02", "exchTradeTime": "29-Sep-2025 09:56:59", "netChange": 1.47, "percentChange": 1.35, "avgPrice": 109.54, "tradeVolume": 13328000, "opnInterest": 156960000, "lowerCircuit": 97.7, "upperCircuit": 119.42, "totBuyQuan": 2480000, "totSellQuan": 2736000, "52WeekLow": 0.0, "52WeekHigh": 115.94, "depth": { "buy": [ { "price": 110.02, "quantity": 8000, "orders": 1 }, { "price": 110.01, "quantity": 8000, "orders": 1 }, { "price": 109.99, "quantity": 16000, "orders": 2 }, { "price": 109.98, "quantity": 16000, "orders": 2 }, { "price": 109.97, "quantity": 24000, "orders": 3 } ], "sell": [ { "price": 110.09, "quantity": 8000, "orders": 1 }, { "price": 110.1, "quantity": 24000, "orders": 2 }, { "price": 110.11, "quantity": 8000, "orders": 1 }, { "price": 110.12, "quantity": 8000, "orders": 1 }, { "price": 110.13, "quantity": 8000, "orders": 1 } ] } } ], "unfetched": [] } } -
Facing same issue with index options ltp data
-
@smalgo Thank you!
@admin Could you please escalate this to your team as soon as possible?
This issue is breaking our algo and impacting live trading. Stability is critical — we’d much prefer things to be reliable rather than having to firefight during market hours.
It appears to be a widespread issue. On our end, all F&O instruments are affected — the API is returning only the base symbol instead of the full contract identifier (TRADINGSYMBOL).
We’d really appreciate urgent attention to this.
New Response
{ "status": true, "message": "SUCCESS", "errorcode": "", "data": { "fetched": [ { "exchange": "NFO", "tradingSymbol": "PNB", "symbolToken": "52500", "ltp": 110.61, "open": 108.94, "high": 110.69, "low": 108.94, "close": 108.56,Old Response
{ "status": true, "message": "SUCCESS", "errorcode": "", "data": { "fetched": [ { "exchange": "NFO", "tradingSymbol": "CUB26SEP24140PE", "symbolToken": "108288", "ltp": 0.15, "open": 0.2, "high": 0.2, "low": 0.15, "close": 0.15, "lastTradeQty": 15000,t -
Hi all, checking the issue.
-
Admin, we are still having issues with quotes, LTP.. is anyone working on it?
-
Hi All, it has been fixed.
-
@admin
Thank you — we truly appreciate your support.Could you please ask your team to handle production-level changes with greater care and ensure clear communication with the community in advance? This is not only critical but also a basic courtesy and expectation. Unannounced or unmonitored changes can potentially lead to significant losses, especially considering that many of us rely on automated systems (algorithms) precisely so we don’t have to monitor everything manually in real time.
As a humble request, we ask that you provide a more reliable and transparent system moving forward.
Additionally, could you please share a root cause analysis of what happened in this instance? Understanding the issue will help everyone avoid similar problems in the future.
Thank you again.
-
Hey,
Issue still persist, I am not getting response from below URL
https://apiconnect.angelone.in/rest/secure/angelbroking/order/v1/getLtpData
The requested URL was rejected. Please consult with your administrator.
Your support ID is: 13207413113617156603
[Go Back]