Request market Data feed access

Developer API
1

Hi Upstox Team,

I’ve created a developer app named API first on 02/10/2025. My access token works for historical APIs, but I’m not receiving any data from the WebSocket v3 feed. Kindly enable market data feed access for my app. My Client ID is: 5c82a380-7fd8-4bbe-8252-e8652fa4b62e.

Thanks!

2

Hi @Bhavika_49359057
The Historical API is an open API, and it is optional to include an access token in the request.
However, the WebSocket v3 endpoint is secured and requires access token validation.

Please regenerate your access token and try again, as your current token may have expired.

Thanks!

3

Additionally, no extra enabling of the Market Data Feeder is required — it is open for all Upstox users.

4

Thank you for reply but the issue still remains.

I have refactored my code to be extremely fast. It generates a new access token, immediately uses it to get a v3 feed URL, and the WebSocket library sends the subscription message within milliseconds of the connection opening. We have proven the subscription message is sent successfully. However, the server stream remains silent—no data, no heartbeats. This strongly suggests the authorization token embedded in the feed URL is expiring almost instantly. Can you please confirm the exact lifecycle and validity period of this token, and check your logs for my API key to see why the data stream is not being initiated after my successful subscription?

5

Hi @Bhavika_49359057 This might be helpful

6

I referred to the example but still the problem persists.

The issue is that I am not receiving any data from the V3 WebSocket feed after a successful connection and subscription.

I have conducted extensive debugging and can confirm the following:

  1. My application successfully generates a v2 access token.

  2. It uses this token to successfully authorize and fetch a v3 WebSocket URL.

  3. The connection to this URL is opened successfully.

  4. My application then sends a binary-encoded Protobuf subscription payload, which is structured exactly according to your official GitHub example for the V3 API.

  5. The subscription message is sent successfully without any client-side errors. The connection remains open and stable (confirmed with client-side keep-alive pings).

Despite all these successful steps, the server remains completely silent during live market hours. It does not send any market data packets (md.feed), nor does it send any md.heartbeat messages.

My API Key is: [5c82a380-7fd8-4bbe-8252-e8652fa4b62e]

Could you please investigate your server-side logs for my API key to determine why the data stream is not being sent?

Thank you.