Today, I encountered a situation that I feel is important to highlight—not to point fingers, but to suggest a more constructive approach for the future.
For the past few days, I have been in contact with the Fyers API team regarding a specific issue: the depth function was returning incorrect bid/ask data when multiple symbols were requested. Rather than addressing the underlying bug, the team simply blocked the ability to pass multiple symbols entirely—a feature that was previously functional.
This approach reminds me of the “ostrich effect”—burying one’s head in the sand to ignore a problem rather than solving it. I think restricting features to avoid fixing bugs hinders the product’s growth.
I request to the entire Fyers team and the leadership with my petty experience to change this approach toward handling any issue you come across in future.
All the best, thank you for the support and keep growing.
Hi @106602805869365269166,
Thank you for your feedback. I understand your concern and agree with you.
I would like to highlight that the Depth API was originally designed to provide data for one symbol at a time. Due to an issue, it temporarily allowed multiple symbols, which resulted in duplicate values and incorrect data.
Supporting multiple symbols requires thorough testing, as incorrect data can lead to consequences like incorrect trade decisions.
We are committed to ensuring high-quality data. Based on your feedback, we will work on enabling support for multiple symbols with accurate data.
Stay tuned. Thank you.
Hello Naresh,
To clarify, the Depth API was not designed for single symbols, I was using it for long time, without knowing the highlighted issue, the day I noticed and highlighted this to the team, they just made changes allowing single symbol only. I understand such issue can’t be noticed and resolved very next movement, but the approach of solving it actually disturbed and made me highlight it here on forum
Having been part of the Fyers family for a long time, based on the experience I know the team will resolve this issue, I have that confidence, just expecting a follow back once the issue is resolved as that matters me the most.
Thank you, keep going.
Thank you for your understanding.
The issue is that, for some users, multiple symbols were being allowed, while for others, it was working as expected. However, we understand the importance of this. Please be assured that this has been added to our enhancement list, and we will implement it soon.