Websocket 403 error on analytics token

@Ankit_48575357 Market Data Feed V3 WebSocket returns 403 Forbidden on upgrade despite successful authorize Developer API Hi @SATYAM_2286284 Some common causes for 403 Forbidden during the WebSocket handshake are: Using the authorized_redirect_uri more than once. The URL returned by the authorize endpoint is single-use and a fresh one must be generated for every new WebSocket connection. Reusing an existing WebSocket connection without closing it properly before establishing a new one.