Market Data Feed v3 - Multiple Web Socket Connections?

Developer API
1

Hello,

After I got sick of every day filled with issues with UPSTOX web sockets v2, I finally decided to upgrade to the market data feed v3, but facing issues here too. Getting an HTTP 403 while opening multiple web socket connections in parallel. It’s working in the current v2 WSS endpoint.

I would like to know the reason behind this HTTP 403? Is opening multiple web socket connections (obviously for different symbols) no longer supported? Or am I doing anything wrong? I’m using a custom C# application. And by the way, I had to generate MarketDataFeed C# classes by my own as your Github repo still doesn’t have any mention of v3 of data feed.

I tried by creating multiple apps under my profile and used different access tokens but still couldn’t open multiple socket connections. I hope I get it wrong but if multiple web socket connections per user is actually not supported anymore then I would say it’s an extremely poor design decision. I believe someone at UPSTOX didn’t have the foresight that people might be having different applications that need separate socket connections in parallel. But like I said, I hope I am wrong here.

Let me know why it no longer works. I’m eager to know that.

2

For basic plan They are allowing 2 connection at a time and for Plus plan 5 connections are allowed. In one connection you can subscribe to 2000 scrips.

3

Hi Jagdish, thanks for your reply.

Yes, I read that part and I completely agree. But I have more than two mutually exclusive, independently running custom apps:

  • an API (as a TradingView webhook for placing NIFTY/BNF options orders)
  • a Windows app (for managing NIFTY/BNF positions)
  • another Windows app for equities

In an ideal scenario, I should be able to create three UPSTOX apps in my profile, generate three separate access tokens - each for one app, correct?

In practical sense, the real limit should be on the number of apps a user is allowed to create. If I can create “n” number of apps, then I should be able to generate “n” access tokens. Thereafter, how I use that token within the app that should be up to me - whether I use that token for opening a web socket connection or polling the server for quotes or create orders, that shouldn’t matter at all. Currently, this is not the case.

Keeping this aside, with different apps, different access tokens too, I’m not able to open more than one web socket connections. Every time I have one socket open, the 2nd one fails with HTTP 403. I don’t know what’s going wrong. And there’s no issue with the code, as everything is still working with version 2 of the Market Feed socket endpoint.

4

Hi @Agent007

As @Jagdish_j_ptl pointed out, you can access upto 2 connections under the basic plan and upto 5 under the plus plan.

This limit is on the client level instead of the app level.

5

Hello @MohitGolecha ,

Thanks for your quick response. As I said, I already read the documentation and completely understood what it meant. My point was the UPSTOX management should realise their one decision can set back days or even months of hard work of their users.

Anyways, now that UPSTOX is offering Pro for free, I can only hope that once users upgrade to Pro for free and build dependent systems based on the revised Pro limits, UPSTOX doesn’t take an overnight decision to charge for the Pro plan.