https://v2.webnotes.in/tags/developer-console/Recent content in Developer Console on WebNotesHugoen-INTue, 12 May 2026 00:00:00 +0000https://v2.webnotes.in/how-to-generate-kite-connect-api-key/Tue, 12 May 2026 00:00:00 +0000https://v2.webnotes.in/how-to-generate-kite-connect-api-key/<p>The <a href="https://v2.webnotes.in/kite-connect-api/">Kite Connect API</a> requires a valid <code>api_key</code> and <code>api_secret</code> pair to authenticate every session and API call. These credentials are issued by <a href="https://v2.webnotes.in/zerodha/">Zerodha&rsquo;s</a> developer console at kite.trade after you register an app and subscribe to the Kite Connect service. This guide walks through every step of that process.</p> <aside class="callout callout--key" role="note"> <strong class="callout__label">Prerequisites</strong> <div class="callout__body"><ul> <li>A fully KYC-verified and active Zerodha trading account. Open one at zerodha.com if you do not have one.</li> <li>A Zerodha Kite Connect subscription (Rs 2,000/month). The subscription is billed to your Zerodha client ID.</li> <li>Two-factor authentication (TOTP) set up on your Zerodha account. This is mandatory for logging in to the developer console.</li> <li>A redirect URL where Zerodha will send users after they authorise your app. For testing, <code>http://127.0.0.1</code> is acceptable.</li> </ul> </div> </aside> <aside class="callout callout--info" role="note"> <strong class="callout__label">Conflict-of-interest disclosure</strong> <div class="callout__body">WebNotes is an independent knowledge base. This guide is not sponsored by Zerodha or any third party. Links to kite.trade and zerodha.com are informational only.</div> </aside> <h2 id="why-kite-connect-requires-an-api-key">Why Kite Connect requires an API key</h2> <p><a href="https://v2.webnotes.in/kite-connect-api/">Kite Connect</a> authenticates API clients using a two-credential model: the <code>api_key</code> (an identifier, safe to share with users of your app) and the <code>api_secret</code> (a private signing credential that must never be exposed). Every authenticated session begins with the OAuth-style login flow that uses both credentials to produce a short-lived <code>access_token</code>. The <code>api_key</code> also governs which Zerodha client IDs your app is authorised to act for, and is the billing identifier that Zerodha uses to track subscription status and usage.</p>