Visma,   I'm in the progress of connecting to the Visma.net API. I ran into an issue where our application doesn't handle the Visma.net oAuth authorization correctly. The reason for this is that the Visma.net implementation differs from the standard.   When I mean standard, I refer to the https://www.oauth.com/ website and the standard that's described there. I was wondering why Visma.net has chosen to divert from this standard and if it's possible to get the standard responses instead of the custom Visma.net response.   To elaborate: Authorization Request - Identical to standard described on  https://www.oauth.com/ Authorization Response - Identical to standard described on  https://www.oauth.com/ Access Token Request - Identical to standard described on  https://www.oauth.com/ Access Token Response – Not identical!   https://www.oauth.com/oauth2-servers/access-tokens/access-token-response/ describes the response as follows:   HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store Pragma: no-cache   {   "access_token":"MTQ0NjJkZmQ5OTM2NDE1ZTZjNGZmZjI3",   "token_type":"bearer",   "expires_in":3600,   "refresh_token":"IwOGYzYTlmM2YxOTQ5MGE3YmNmMDFkNTVk",   "scope":"create" }   Visma.net response is:   HTTP/1.1 200 OK Content-Type: application/json Cache-Control: no-store Pragma: no-cache   {   "token":"1f729814-1a98-4c8e-860b-76ec004742f5",   "token_type":"bearer",   "scope":"financialstasks" }   My question is: Is there a way for me the get the standard response format as described on https://www.oauth.com/   A thing I did notice is that Visma eAccounting API DOES return the responses formatted the same as described in the standard, so Visma.net seems to be the odd one out. Is this on purpose and how do I get around this without recoding our generic oAuth2 implementation with an exception for Visma.net?   Thanks in advance! ... View more