Invalid Access Token After API Secret Regeneration — Despite Correct Checksum and Request Token

kvnkelly9

I'm encountering a persistent issue with the Kite Connect API:

I regenerated my API secret from the developer console

I’m using fresh request tokens immediately after login

I’m generating the checksum using SHA256 in the format: api_key + request_token + api_secret

I’m sending a POST request to https://api.kite.trade/session/token with headers: Content-Type: application/x-www-form-urlencoded

All parameters are correct and verified

I’ve tried multiple implementations and cleared sessions

Despite this, I consistently receive an “invalid access token” error.
Details:

API Key: XXXXXXX

Most recent request token: v7D4jp403TjLZ4CdArxzRfyKyG3Kf8U0

Client: pykiteconnect

Kite Connect API version: v3

Timestamp of last attempt: 16 Oct 2025, 10:00 AM IST

This issue is blocking my production trading platform. Please advise if there’s a backend issue with my app configuration or if the regenerated secret needs to be reset internally.

nagavenij

You may refer to this forum discussion.