[Issue with oauth2.0 access token]

Just fixed the problem. 

The problem was that I was using the code exactly as it came from the URL (encoded): GB%2Fxxxxxxxxxxxxxxx and that does not work. I've decoded the code, becoming something like: GB/xxxxxxxxxxxx and now it works.

An easy fix actually, but I've overlooked it. Since this seems to be an often asked question, I hope this may help someone save a few hours. 

[Issue with oauth2.0 access token]

1 hour ago, Steel, Mark said:

Hi Joshua, thank you for your question.

Could you confirm the following please?

You're making a POST request to https://oauth.accounting.sage.com/token containing:
Header param of Content-type: application/x-www-form-urlencoded
And Body Params made up of:

• client_id
• client_secret
• code
• grant_type
• redirect_uri

Have you been able to authenticate in a web client tool such as Postman?

Hi Steel, Mark, thanks for your answer.

Yes. It is a POST request to: https://oauth.accounting.sage.com/token
Content-type: application/x-www-form-urlencoded
Body Params as your refered, yes. Tried both with params URL encoded and normal. 

I'm using Postman, that's where I'm getting the error. I'm not really sure about what I could try more. 

[Issue with oauth2.0 access token]

Hi, I have the exact same issue, when exchanging code for access token: 

https://oauth.accounting.sage.com/token

 

Content-type: application/x-www-form-urlencoded

Grant_type: 'authorization_code'

Access token from redirect URI: ?code=GB%2F89cf3e2b-4cf8-46e4-80e3-47828e6dd542&country=GB

I've already tried with, for the parameter "code": 

'89cf3e2b-4cf8-46e4-80e3-47828e6dd542'
'GB%2F89cf3e2b-4cf8-46e4-80e3-47828e6dd542'
'Bearer GB%2F89cf3e2b-4cf8-46e4-80e3-47828e6dd542'
'Bearer 89cf3e2b-4cf8-46e4-80e3-47828e6dd542'

 

But all return the following error: "The auth code you transmitted has an unexpected format."

I've also tried to URL Encode all parameters, still not working. Any ideas?