<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kite Login on WebNotes</title><link>https://v2.webnotes.in/tags/kite-login/</link><description>Recent content in Kite Login on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/tags/kite-login/index.xml" rel="self" type="application/rss+xml"/><item><title>Kite Connect authentication errors: invalid app code and incorrect api_key or access_token</title><link>https://v2.webnotes.in/kite-connect-auth-errors/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/kite-connect-auth-errors/</guid><description>&lt;p&gt;&lt;strong&gt;Kite Connect authentication errors&lt;/strong&gt; fall into two layers that are often confused: the human Kite login, where &amp;ldquo;Invalid app code&amp;rdquo; means the second-factor code failed, and the &lt;a href="https://v2.webnotes.in/kite-connect-api/"&gt;Kite Connect API&lt;/a&gt;
, where &amp;ldquo;Incorrect api_key or access_token&amp;rdquo; means a programmatic session is invalid or expired. The first is almost always a device-clock problem on the time-based login code; the second is almost always the daily 6 a.m. expiry of a Kite Connect access token, returned to your program as an HTTP 403 with a TokenException. They look similar because both involve a token and both block access, but they sit at different layers and have different fixes.&lt;/p&gt;</description></item><item><title>How to disable TOTP on Zerodha Kite</title><link>https://v2.webnotes.in/how-to-disable-totp-zerodha/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-disable-totp-zerodha/</guid><description>&lt;p&gt;&lt;strong&gt;To disable TOTP on &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
, log in, open My profile then Password &amp;amp; security, click Disable external TOTP, enter your Kite login password, and click Disable; the account then reverts to the &lt;a href="https://v2.webnotes.in/sms-otp/" rel="nofollow"&gt;SMS OTP&lt;/a&gt;
 as its second factor.&lt;/strong&gt; You cannot switch the second factor off entirely, because two-factor authentication on a trading login is mandated by the exchanges and SEBI.&lt;/p&gt;
&lt;p&gt;This is the point most people miss. &amp;ldquo;Disable TOTP&amp;rdquo; does not mean &amp;ldquo;log in with just a password.&amp;rdquo; It means swap the time-based app code back for the text-message code. One second factor always remains. Zerodha&amp;rsquo;s support pages are explicit that the OTP step at login cannot be eliminated, only changed in form.&lt;/p&gt;</description></item><item><title>How to fix the Invalid TOTP error on Zerodha Kite</title><link>https://v2.webnotes.in/how-to-fix-invalid-totp-zerodha/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-fix-invalid-totp-zerodha/</guid><description>&lt;p&gt;&lt;strong&gt;The Invalid TOTP error on &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 is a clock problem, not a wrong code: Kite rejects the &lt;a href="https://v2.webnotes.in/how-to-set-up-totp-zerodha/"&gt;TOTP&lt;/a&gt;
 when the clock on the device running your authenticator does not match network time, so set that phone to automatic or network-provided time and enter a fresh six-digit code.&lt;/strong&gt; TOTP is time-based; a drift of even a minute makes the app compute the code for the wrong 30-second window, and Kite refuses it.&lt;/p&gt;
&lt;p&gt;This is the single most common cause, and it is also the least obvious one, because the code on screen looks perfectly valid. It is valid, for a moment that has already passed or not yet arrived. The fix is to correct the clock on the device that generates the code, which is the phone holding Google Authenticator or Authy, not the computer you are logging in from.&lt;/p&gt;</description></item><item><title>How to recover a lost TOTP on Zerodha Kite</title><link>https://v2.webnotes.in/how-to-recover-lost-totp-zerodha/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-recover-lost-totp-zerodha/</guid><description>&lt;p&gt;&lt;strong&gt;If you lost the phone holding your authenticator, deleted the app, or wiped the device, recover access on &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 by clicking Forgot user ID or password? on the login page; verify with your user ID, PAN, and an OTP to your registered email or mobile, set a new password, then re-enrol TOTP under Method 2: External authenticator and scan a fresh QR code.&lt;/strong&gt; The standard reset is self-service and free; no support ticket is needed unless you have also lost access to both your registered email and mobile.&lt;/p&gt;</description></item><item><title>How to remove the temporary OTP on Kite</title><link>https://v2.webnotes.in/how-to-remove-temporary-otp-kite/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-remove-temporary-otp-kite/</guid><description>&lt;p&gt;&lt;strong&gt;You cannot remove the temporary OTP step on &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
, because NSE and &lt;a href="https://v2.webnotes.in/sebi/"&gt;SEBI&lt;/a&gt;
 require a second authentication factor on every trading login; what you can do is switch the temporary OTP from an SMS-delivered code to an authenticator-generated &lt;a href="https://v2.webnotes.in/how-to-set-up-totp-zerodha/"&gt;TOTP&lt;/a&gt;
, under My profile then Password &amp;amp; security.&lt;/strong&gt; The OTP step itself is mandatory and stays; only its form is yours to choose.&lt;/p&gt;
&lt;p&gt;The phrase &amp;ldquo;temporary OTP&amp;rdquo; describes the time-limited one-time password Kite asks for after your password at each login. It is temporary in the literal sense: each code is valid for a short window, about 30 seconds for an authenticator code, then expires. People searching to &amp;ldquo;remove&amp;rdquo; it usually mean one of two things: they want to stop the SMS-delivered OTP and use something smoother, or Zerodha issued them a one-off temporary access after a lockout and they want to know how to get back to a normal login. This guide covers both.&lt;/p&gt;</description></item><item><title>How to set up TOTP on Zerodha Kite</title><link>https://v2.webnotes.in/how-to-set-up-totp-zerodha/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/how-to-set-up-totp-zerodha/</guid><description>&lt;p&gt;&lt;strong&gt;TOTP, or time-based one-time password, is a six-digit code that an authenticator app on your phone generates offline and refreshes every 30 seconds; on &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 you enable it under My profile, Password &amp;amp; security, Enable external TOTP, then scan a QR code with &lt;a href="https://v2.webnotes.in/google-authenticator/" rel="nofollow"&gt;Google Authenticator&lt;/a&gt;
 or &lt;a href="https://v2.webnotes.in/authy/" rel="nofollow"&gt;Authy&lt;/a&gt;
 so the rolling app code becomes your second login factor in place of the SMS OTP.&lt;/strong&gt; Setting it up takes about five minutes and costs nothing.&lt;/p&gt;</description></item><item><title>Kite app code: what it is and how it works as a login factor</title><link>https://v2.webnotes.in/kite-app-code/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/kite-app-code/</guid><description>&lt;p&gt;The &lt;strong&gt;Kite app code&lt;/strong&gt; is a six-digit time-based one-time password (TOTP) generated inside Zerodha&amp;rsquo;s &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 mobile app that you type into &lt;a href="https://v2.webnotes.in/kite-web/"&gt;Kite web&lt;/a&gt;
 as the second factor of a two-factor login. After you enter your user ID and password on Kite web, the app shows a code that is valid for 30 seconds; entering it completes the login. Zerodha documents this as the default second factor for clients who have the Kite mobile app and have not switched to an external authenticator.&lt;/p&gt;</description></item><item><title>Why Kite shows the risk disclosure at every login</title><link>https://v2.webnotes.in/why-risk-disclosure-every-login-kite/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/why-risk-disclosure-every-login-kite/</guid><description>&lt;p&gt;Kite shows the SEBI risk disclosure at every login because a SEBI circular requires every stock broker to display it and to let clients proceed only after acknowledging it. The circular, SEBI/HO/MIRSD/MIRSD-PoD-1/P/CIR/2023/73 dated 19 May 2023 and in force from 1 July 2023, followed a SEBI study finding that 9 out of 10 individual traders in the equity futures and options segment lose money. The disclosure is not a Zerodha choice; it is a regulatory mandate, and &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 implements it as the half-screen pop-up you acknowledge each day.&lt;/p&gt;</description></item><item><title>Zerodha client password and credential policy</title><link>https://v2.webnotes.in/zerodha-client-password-policy/</link><pubDate>Sat, 20 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/zerodha-client-password-policy/</guid><description>&lt;p&gt;&lt;strong&gt;Zerodha&amp;rsquo;s client password and credential policy&lt;/strong&gt; sets no password in the account-opening welcome email; the client creates the password at first login, and a mandatory second factor, the Kite App Code or an external time-based one-time password (TOTP), sits on top of it under the cyber-security framework SEBI mandated in its circular of 3 December 2018, enforced across brokers from 30 September 2022. The login is therefore two factors deep by design, and the account holder, not the broker, carries the loss from any credential misuse.&lt;/p&gt;</description></item></channel></rss>