Forum

Hello! I’m trying to get my refresh token by following the procedure described here as I’ve been doing for years, but once I get the code from the authorize endpoint, the token endpoint returns 400 bad request and the following message:

“error”: “invalid_parameter”,

“error_description”: “One or more properties have errors or are missing.clientId is required”

Any suggestion? I’ve used this exact same sequence for years without any issue. Also, I’ve just noticed that the procedure mentioned above is not clear, as it mentions to use OAuth2 as the authorization type, which is something I never did in the past and anyway it doesn’t specify which parameters to use in that section.

Thanks in advance for any hint!

• This topic was modified 3 months, 4 weeks ago by ilgioa.

Hello,

Indeed I reproduced the error on my side. In Postman, you can switch to x-www-form-urlencoded to fix the problem. I asked the teams if it’s possible to make form-data working back, I’m waiting for their answer

Have a good day,

Leslie – Community Manager

Hi, thanks for the answer and apologies for the late feedback. I’ve tried x-www-form-urlencoded with the same parameters but I get a “not valid segment token” error. See screenshot.

Please advise. Thanks!

• This reply was modified 3 months, 1 week ago by ilgioa.

Hello,

For information, the “form-data” problem is fixed and should work back as normal

I think you don’t correctly take the “code” value. Beware to stop at the “&idToken” part. Otherwise, all other parameters for your request seem OK for me

Have a good day,

Leslie – Community Manager

Still not working for me.

I query the authorize endpoint and receive a code, that I then use it with the token endpoint, which still returns a “invalid grant” error.

• This reply was modified 3 months ago by ilgioa.

Can you send me the code value you use in the /token request ? You can use our contact form for this 

Have a good day,

Leslie – Community Manager

Just sent a message, thanks.