Login failed: Error from Dhan: Dhan Consent API Failed: [CONSENT_LIMIT_EXCEED] Consent limit Exceeded
Last updated 8 October 2026
Dhan login errors (DH-906, Consent limit, TOTP, RS-0060)
DH-906 Invalid Token means Dhan ended your session. On the auto-login platform DHAN_V2_AT_IPV6, AutoTrader Web logs in again on its own, so just try again. Consent limit, TOTP and RS-0060 errors are intermittent bugs on Dhan's side. For those, switch to the manual DHAN_V2_IPV6 platform, where you paste the access token yourself each day.
When this happens
- 1 DH-906 Invalid Token: Dhan ended the session AutoTrader Web was using.
- 2 Consent limit, TOTP and RS-0060: intermittent bugs on Dhan's side, not on your account.
- 3 Dhan's connection or consent APIs fail or rate-limit during the daily connection.
Errors
This fix applies to these Dhan login errors:
- Login failed: Error from Dhan: Dhan Consent API Failed: [CONSENT_LIMIT_EXCEED] Consent limit Exceeded
- Login failed: Error from Dhan: [DH-906 - Invalid Token]
- Login failed: Error from Dhan: TOTP Validation Failed: [RS-0060] Too many requests, please try again after some time
- Login failed: Error from Dhan: TOTP Rejected by Server (isValid: false). Check Time/Clock Sync
DH-906 Invalid Token: just try again
DH-906 - Invalid Token means Dhan ended the session AutoTrader Web was using. This can happen at any time of day, even after a successful morning login. One possible cause is logging in to the same Dhan account somewhere else.
- Auto-login accounts (
DHAN_V2_AT_IPV6): you do not need to do anything. AutoTrader Web logs in again on its own. Retry the failed read or order. An order that hit the error was not placed, so place it again. - Pasted-token accounts (
DHAN_V2_IPV6): the token you pasted is no longer valid. Generate a new access token on Dhan and update it on your account in Accounts → Trading Accounts, then click Validate & Save.
If you moved a Dhan account to DHAN_V2_IPV6 only because of DH-906, you can move it back to DHAN_V2_AT_IPV6 (API key, secret, TOTP and MPIN), so you no longer paste a token every day.
Why the other errors happen
The consent limit, TOTP and RS-0060 errors are mostly bugs on Dhan’s side. They happen while the DHAN_V2_AT_IPV6 platform connects to your account. They do not happen all the time. They come and go, so they are hard to get fixed. We have already reported them to Dhan many times.
How to fix the other errors
Switch your Dhan account to the manual DHAN_V2_IPV6 platform. On that platform you generate the access token yourself each day and paste it into our system, so the automatic connection step that causes these errors is skipped.
See the Dhan setup guide for the exact steps for the DHAN_V2_IPV6 platform.
Note: For “TOTP Rejected by Server (isValid: false)”, also check that the clock on your phone (and your authenticator app) is set to automatic/network time. A wrong clock makes the TOTP fail.
If Dhan asks you to regenerate the API token
If the error says “Please regenerate the API token on Dhan & update in our system”, your Dhan API token is no longer valid. Log in to Dhan, generate a fresh API access token, then update it on your account in Accounts → Trading Accounts and click Validate & Save.
DH-906 during order placement means something different
DH-906 has two different meanings depending on when it appears:
- At login, or on a read during the day, it means Invalid Token. See DH-906 Invalid Token above.
- While placing an order it appears as “DH-906 - Exchange Segment Not Activated, Not able to proceed”. This is not a login problem: the trading segment (for example F&O) is not active on your Dhan account. Activate that segment with Dhan and place the order again. See Segment not enabled for your account.
