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.
Sign In or Register to comment.