Apologies, I am perplexed. Has something changed with how API calls are handled in the past year. I had code that was working but now I get the above error. Has there been a URL change or perhaps formatting? I am using "3-legged OAuth flow authorization code" Thanks, Andy
Private windows desktop
The change for that platform type is that it will no longer support password flow. However, you said that you have problem to login with 3-legged OAuth and you app is an old app? Please confirm and give me your app client id so I can check for you.
Your app was created on Sep 6, and it is a Desktop/Windows platform type which allows only 3-legged authorization flow. However, you have not specified the OAuth redirect URI for your app so I don't think that you could ever login your app with 3-legged authorization flow.
If you really need 3-legged authorization flow, specify the redirect URI and implement your app to handle the authorization code accordingly. https://developers.ringcentral.com/guide/authentication/auth-code-flow
If you just want to have password flow, create a new app with Server-only platform type. Or let me know so I can help change your current app platform type. https://developers.ringcentral.com/guide/authentication/password-flow
Review what? See my instructions in the previous comment and make your choice.
5 People are following this question.
