Websocket Registration fails on Paid connect Account with 403 Forbidden

UTL879
Paid Connect Account is Active through 18 Oct 2026, REST quote/historical_data succeed, and KiteTicker upgrade returns 403. Please check WebSocket on My-New-Trading-App
  • UTL879
    Paid Connect is Active, REST quote/historical_data work on the same key, and only wss://ws.kite.trade upgrade returns 403.
  • UTL879
    Client: kiteconnect 5.2.2, Python, KiteTicker(api_key, access_token)
    Exact close: 1006 / WebSocket connection upgrade failed (403 - Forbidden)
    on_connect never fires
    Same IP is working for REST quote
  • salim_chisty
    Please verify that you are using a Kite Connect (paid) app's API_Key. Please generate a fresh access_token for the same API_Key and check. You may refer to the similar discussion here.
  • UTL879
    Please check the image , it shows its a connect App
  • UTL879
    Screenshot already shows Connect, active through 18 Oct 2026
    Fresh token generated 21 Sep 2026 for that app
    profile + quote OK on the same session
    KiteTicker(api_key, access_token) still upgrade failed (403)
    Please check streaming / ticker on My-New-Trading-App (REST market data works; only wss://ws.kite.trade does not)
  • salim_chisty
    We have checked this and verified it at our end, and we didn't observe any issues with the WebSocket connection.

    Please review the WebSocket example code and ensure you are using the correct instrument token from the instrument file to check for any errors. Additionally, you can refer to the Python WebSocket streaming FAQs for further guidance.
Sign In or Register to comment.