@admin Hi...
I’m trying to authenticate my SmartAPI app programmatically using MPIN + TOTP.
When I call the login endpoint (https://apiconnect.angelone.in/rest/auth/angelbroking/user/v1/loginByMpin),
the API gateway returns an HTML “Request Rejected” page instead of JSON.
The issue appears to be on the WAF/gateway layer.
Here are the support IDs generated during my attempts:
11546798736919622241
12752376862828581406
12752376862840471484
12752376862844826990
12752376862821701604
Please check these IDs in the gateway logs and confirm:
- Which endpoint should be used for MPIN login in SmartAPI (MPIN + TOTP flow)?
- Whether my SmartAPI app needs whitelisting or additional headers.
- If you can enable the correct loginByMpin / generateSessionByMpin endpoint for my app.
SmartAPI App Name: MYAlgoBot
Client ID: G210232
Time of attempts: 2025-11-08 around 11:20 PM IST
Public IP used: 182.65.98.159