Urgent Issue: No Data Stream from WebSocket v3 API After Successful Subscription

Developer API
1

Dear Upstox API Support Team,

I am writing to report a persistent issue with the WebSocket v3 API where I am not receiving any data after a successful connection and subscription. I have been troubleshooting this for several days and have ruled out all client-side code and environmental issues.

My Client ID is: 3ff081af-2662-4281-b030-ba0a2edcbc83

The Core Problem:

My application correctly performs the entire documented connection process:

  1. It first makes a request to the /v3/feed/market-data-feed/authorize endpoint.

  2. It successfully receives a unique, one-time-use wss:// URL.

  3. It connects to this authorized URL, and the connection is established successfully.

  4. It sends a subscription request for the instruments NSE_EQ|INE002A01018 and NSE_INDEX|India VIX in full_d30 mode.

  5. My application logs confirm that the subscription message is sent successfully.

However, after the subscription is confirmed, no data packets of any kind are ever received. The WebSocket connection remains open but completely silent. There are no trade updates, no depth-of-market updates, and no error messages.

Log Proof of Successful Connection:

Here is a clean log snippet from my application, showing the successful connection and subscription, followed by silence (no data is received after the last log entry).

2025-07-30 14:56:30,891 [INFO] Authorizing WebSocket feed...
2025-07-30 14:56:32,135 [INFO] (Success) Authorized and received WebSocket URL.
2025-07-30 14:56:32,717 [INFO] WebSocket (v3) connected successfully to authorized URL.
2025-07-30 14:56:32,719 [INFO] Subscribed to ['NSE_EQ|INE002A01018', 'NSE_INDEX|India VIX'] in full_d30 mode via WebSocket V3

Exhaustive Troubleshooting Performed:

I have already performed extensive troubleshooting and can confirm the following:

  • The issue is not related to local firewalls, antivirus software, or VPNs.

  • The issue is not related to network connectivity (tested on multiple networks).

  • The issue is not a Python environment or SSL/TLS incompatibility (tested across multiple Python and library versions, now using a stable Python 3.11 environment).

  • The issue is not with the client-side code’s logic (it has been tested and simplified to a minimal test case, which still exhibits the same problem).

  • The issue is not with handling different message types (e.g., market_info messages), as the connection receives no messages at all.

The evidence strongly suggests that after a successful authentication and subscription, the Upstox server is not streaming any data to my session for the requested instruments.

Could you please investigate your server-side logs for my Client ID to determine why no data is being sent to my active and subscribed WebSocket connection?

Thank you for your time and assistance in resolving this matter.

Sincerely,

Santosh Kumar Singh

2

facing same issues, did you find solution?

3

Dear Upstox Developer Support Team,

I am writing to seek your urgent assistance with an issue we’ve been facing while integrating the Upstox WebSocket v3 API for real-time market data.

Despite successfully completing the entire authorization and subscription process as per documentation, no actual tick data (e.g., LTP, market depth, etc.) is being received, even though the WebSocket connection stays open and no errors are reported.

Summary of the Integration Approach:

  1. REST API Authorization
    We first call the /v3/feed/market-data-feed/authorize endpoint to obtain a one-time, valid WebSocket URL. This part works perfectly, and we receive the authorized URL.

  2. WebSocket Connection
    We connect to the received WebSocket URL (via secure wss://) — and the connection is successfully established.

  3. Subscription Request
    We sent a proper JSON subscription payload such as:

  4. {
    “guid”: “some-uuid”,
    “method”: “sub”,
    “data”: {
    “mode”: “full”,
    “instrumentKeys”: [“NSE_EQ|INE002A01018”]
    }
    }

  5. I have also tried alternate modes like ltpc and full_d30 and switched between multiple instrument keys from active instruments (NSE_EQ, NSE_FO, NSE_INDEX).

  6. Server Acknowledgement
    We receive a binary acknowledgment from the server, and we also see the regular market_info payload. This suggests that the WebSocket is connected, healthy, and our subscription request is at least being processed.

Diagnostics Already Performed:

  • Confirmed that the instrument keys are valid, active, and trading.

  • Verified that market depth (top 5 levels) for the same instruments is available via the REST API.

  • Tried with multiple instrument keys from different segments: NSE_EQ, NSE_FO, NSE_INDEX, etc.

  • Checked subscription payload format, modes, and binary acknowledgment handling.

  • Ensured no issues with:

    • SSL/TLS or WebSocket protocol version

    • Network environment (tested across networks and machines)

    • Python client code or decoding logic (we’re successfully decoding protobuf and able to process market_info)

  • Waited sufficient time (over 5+ minutes) after subscribing, but no real-time data arrives.

The Problem:

Even after successful connection and subscription, we do not receive any real-time feed updates (tick data, LTP, market depth, trades, etc.) for the subscribed instruments. No errors or disconnects occur, but the feed remains completely silent.

We strongly suspect that this is a server-side entitlement issue, where our Client ID or API Key may not be authorized to receive WebSocket-based market data — despite everything being correctly implemented on our end.

Request for Support:

Could someone from the Upstox API team please review our account’s WebSocket entitlement status? We are fully authenticated, REST APIs work, and we’re actively subscribing to valid instruments — but without any tick data coming through.

Please check:

  • Whether our API key and ID are enabled for WebSocket v3 market data access

  • If there’s any server-side filtering or configuration preventing data from being sent to our session

Account Details (for reference):

  • User ID: 45CZ3K

  • API Key : 2e9af676-a612-4fdf-81ec-5da637dcf94f

  • Instruments tested: “NSE_FO|47231”,“NSE_EQ|INE002A01018”,“NSE_FO|44383” etc.

We would be very grateful if this could be looked into urgently, as this is blocking our integration efforts.

Thank you in advance for your time and support.

Warm regards,

Avi Sharma

4

Yes I am also facing the same issue. Subscription successful. But not getting any data. Just giving below the issue. Pls let me know if any updates?

[WS OPEN] Connected
[WS PING] b’’
[WS SUBSCRIBE REQUEST] {‘guid’: ‘sub-001’, ‘method’: ‘sub’, ‘params’: {‘mode’: ‘full’, ‘instrumentKeys’: [‘NSE_FO|39845’, ‘NSE_FO|39853’]}}
[WS] Subscribed to: [‘NSE_FO|39845’, ‘NSE_FO|39853’]
[WS PING] b’’
[WS PING] b’’
[WS PING] b’’
[WS PING] b’’

5

@SANTOSH_2454972 @Juber_49312377 @Avi_20726921 @VIDHYA_35564364
This might be helpful