Hi,

My Python-generated TOTP matches exactly with my Google Authenticator code, but SmartAPI login always fails with:

"status": false,
"message": "Invalid totp",
"errorcode": "AB1050"

Details:

Client ID: S565246

Python SDK (pyotp)

.env secret exactly as provided, no spaces, uppercase, Base32

PC time synced with NTP

Tested within 2–3 seconds of code refresh

Same result on multiple attempts

I suspect there may be a server-side TOTP validation issue or a recent change in the secret format.
Please check my account’s recent login attempts and confirm the current expected TOTP secret format.

This is blocking all automated logins.
Thanks in advance!

Hello SmartAPI Team,

I am facing a TOTP login issue with the SmartAPI Python SDK.
Details of my setup:

Client ID: S565246

API Key: (provided in .env, verified correct)

TOTP Secret: From SmartAPI, stored in .env exactly as given (Base32 format, no spaces)

MPIN: Correct and working in mobile app

Python Library: pyotp

System Time: Synced with NTP, matches phone time

What’s happening:

The TOTP code generated in Python matches exactly with the one shown in Google Authenticator.

Despite that, every login attempt returns:

"status": false,
"message": "Invalid totp",
"errorcode": "AB1050",
"data": null

Tried 3 attempts with fresh codes; same result every time.

This happens even immediately after generating the TOTP, well within the 30-second validity window.

Steps already tried:

Verified .env secret matches the one provided on SmartAPI portal.

Removed spaces and ensured all uppercase letters.

Synced PC time with internet time servers.

Confirmed Python-generated TOTP = Google Authenticator TOTP.

Retried after waiting a few minutes in case of rate limits.

Sample log:

=== Attempt 1/3 ===
[INFO] Using fresh TOTP: 085893
[RESULT] {'status': False, 'message': 'Invalid totp', 'errorcode': 'AB1050', 'data': None}

Could you please:

Check on your server logs for my Client ID (S565246) for recent login attempts.

Confirm if there is any new format, encoding, or configuration for the ANGEL_TOTP_SECRET.

Let me know if there are any recent changes to the TOTP verification logic.

Thank you,
Swapnil Mahajan!

@admin USERID G39957 Please Migrate to New system

My User ID is G39957 i had reported earlier (15 days back) and request to migrate, till date it has not happened kindly do the needful

@Gopal Reminder -1

USERID G39957 Please Migrate to New system

Please migrate G39957 to new system

USERID G39957 Please Migrate to New system

@admin USERID G39957 Please Migrate to New system

@admin thanks for the reply .. I don't remember having registered through any sub-broker, it was direct with Angel, Anyhow if you wish to migrate the account you may do so. But before i use speed pro, how do i continue to use it,as in post link mentioned by you says we cannot use Speed pro after migrating, Please confirm,

@admin G39957