Persistent 'Invalid Credentials' Error During Upstox Login

I am encountering a persistent issue when attempting to log in to the Upstox using the redirection login flow. Despite providing correct credentials, I consistently receive the following error after entering the 6-digit PIN on the Upstox login screen.

{“status”:“error”,“errors”:[{“errorCode”:“UDAPI100016”,“message”:“Invalid Credentials”,“propertyPath”:null,“invalidValue”:null,“error_code”:“UDAPI100016”,“property_path”:null,“invalid_value”:null}]}

I have double-checked my credentials, ensured the accuracy of the redirect URI, and verified that the API key and secret are correct. Despite these efforts, the issue persists, and I am unable to log in successfully.

Redirect url : http://localhost:8080/login/callback-upstox/

Please investigate this matter and provide guidance on resolving the ‘Invalid Credentials’ error during the redirection login process.

Thank you for your assistance.

@Yamanrb12,

Thank you for reaching out.

Assuming you are using a browser to authenticate to the API, the error you’re encountering may be related to your browser’s settings preventing the setting of a necessary cookie for the authentication process.

Could you please try using a different browser for this task and let us know if the issue persists?

Thank you!

Hello @shanmu Thank you ,

I attempted the same process in a new incognito window, but encountered the same issue. In the new window, the system prompted me to complete the entire login procedure, including entering my mobile number, TOTP (Time-based One-Time Password), and PIN.

@shanmu Any Update ?

@Yamanrb12,

Please provide your UCC and the URL you’re using to initiate the login. For security purposes, you may omit the client_id when sharing this information.

Thanks!

@shanmu
here is the UCC : 197075
and the redirect url : https://api.upstox.com/v2/login/authorization/dialog?response_type=code&client_id=***************&redirect_uri=http%3A%2F%2F127.0.0.1%3A8000%2Flogin%2Fcallback-upstox%2F

@Yamanrb12

We’ve resolved the issue on our end. Please try again and inform us if it’s working for you now.

Thanks!

Yes, its working now, Thank you very much for you support.