question

newuser-40ce6fee-700d-4461-8c4c-bd0f247665eb avatar image

Alexa Account Linking- Oauth2.0 Account Grant type - Unable to link your account

Hello,

We are using OAuth 2.0 Authorization Code Grant type for Alexa Account Linking. Our application is able to authenticate the user and generate authorization code. After this step Alexa is unable to get the access token from our access token uri. So we are getting "Unable to link the account " error message.

Does anyone know how to debug alexa account linking? Or How to check if alexa is hitting access token uri or not?

Any help or guidance would be appreciated.

Thank you

alexa skills kitaccount linking
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Ross@Amazon avatar image
Ross@Amazon answered

Hi,

Please refer to our Alexa Account Linking Debug guide.

1 comment
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Akshar avatar image Akshar commented ·

Hello i have used this bedbug method and i am getting this error stiil this is my response..

{ "access_token": "79a3b369f9bac112eb288565fa314284e5ffd317", "expires_in": 3600, "token_type": "Bearer", "scope": "profile:user_id", "refresh_token": "21f1d2ec78ef64d984b531c70ce5d7af36ae2d29" }
0 Likes 0 ·
Akshar avatar image
Akshar answered

Hello @Ross@Amazon i have tried the debud guide and the response is getting in this format..

now it might be a small error but it will be very easy to find from you so will you please help me and guide through it ..

(40a4545f-c448-11e7-b7bf-71c7b76b99d9) Endpoint request body after transformations: grant_type=authorization_code&code=7b0ea6dafc9eed0f017ca9070d01b03323b71f08&redirect_uri=https%3A%2F%2Flayla.amazon.com%2Fapi%2Fskill%2Flink%2FM3BVP74N95SP1F&client_id=alexa&client_secret=alexa(40a4545f-c448-11e7-b7bf-71c7b76b99d9) Sending request to https://lendinglistsjd.in/alexa/login/token.php(40a4545f-c448-11e7-b7bf-71c7b76b99d9) Received response. Integration latency: 1307 ms(40a4545f-c448-11e7-b7bf-71c7b76b99d9) 

Endpoint response body before transformations:{"access_token": "79a3b369f9bac112eb288565fa314284e5ffd317","expires_in": 3600,"token_type": "Bearer","scope": "profile:user_id","refresh_token": "21f1d2ec78ef64d984b531c70ce5d7af36ae2d29"}

(40a4545f-c448-11e7-b7bf-71c7b76b99d9) 
Endpoint response headers: {Keep-Alive=timeout=5, max=500, Transfer-Encoding=chunked, Server=Apache, Cache-Control=no-store, Connection=Keep-Alive, Pragma=no-cache, Date=Wed, 08 Nov 2017 05:46:47 GMT, Content-Type=application/json;charset=UTF-8}

(40a4545f-c448-11e7-b7bf-71c7b76b99d9) Method response body after transformations:{"access_token": "79a3b369f9bac112eb288565fa314284e5ffd317","expires_in": 3600,"token_type": "Bearer","scope": "profile:user_id","refresh_token": "21f1d2ec78ef64d984b531c70ce5d7af36ae2d29"}

(40a4545f-c448-11e7-b7bf-71c7b76b99d9) Method response headers: {Keep-Alive=timeout=5, max=500, Server=Apache, Cache-Control=no-store, Connection=Keep-Alive, Pragma=no-cache, Date=Wed, 08 Nov 2017 05:46:47 GMT, Content-Type=application/json;charset=UTF-8}
									
10 |5000

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.