Kite Web and KiteConnect sharing same session?

sodha_rakesh

Hi Team,

I am testing KiteConnect basic API to get Ticker.

I noticed the below behavior with KiteWeb and KiteConnect:

• if KiteWeb is running and I start KiteConnect, the KiteWeb gets logged-out
  
• whenever I connect KiteWeb, while Ticker API is running, it throws error:
  kiteconnect.ticker - ERROR - Connection error: 1006 - connection was closed uncleanly (WebSocket connection upgrade failed (403 - Forbidden))
  

1. Does it mean that the AccessToken is share between KiteWeb and KiteConnect?
2. As the order execution disconnects or Log Out users on KiteWeb, does same apply to KiteConnect?
3. Do we need to re-connect or get new access token after executing order API?

Thanks in advance for your inputs

Best Regards,
Rakesh

sujith

You can go through this thread for the solution and the reason we do this.

sodha_rakesh

Thanks @sujith for the reply.

Further questions:
1. The solution in the thread you mentioned.. "The solution is to log in to Kite Connect and then log in on the Kite web." is it still valid?
2. If order placed by Order API, will it require re-login for Ticker ? (in KiteWeb, after order placement, re-login is required)

sujith

1. Yes, you can try it out.
2. No, you don't need to re-login.

sodha_rakesh

Thank you very much @sujith for the confirmation