Alexa Skill Account Linking – Getting ‘Unable to link skill at this time’ even after correct Redirect URI, Client ID/Secret, and CORS setup

Try this for the bebugging:

1. Check Server Logs During Linking Attempt

• Log incoming requests to your token endpoint and authorization endpoint. • Look for malformed requests, missing headers, or failed token exchanges. • Confirm that the Content-Type is set to application/json and that the token response includes all required fields: access_token, token_type, expires_in, and optionally refresh_token. 2. Use Alexa Developer Console Logs

• Use the Test tab in the Alexa Developer Console to simulate account linking. • Watch for any error messages or failed redirects. • If you’re using Alexa-hosted skills, CloudWatch logs may capture some backend errors. 3. Enable CloudWatch for Lambda

• Ensure CloudWatch logging is enabled. • Check logs for any errors during the account linking flow. 4. Validate Token Endpoint Accessibility Alexa must be able to reach your token endpoint: • Test it with tools like curl or Postman from an external network. • Confirm that SSL certificates are valid and publicly trusted. 5. Refresh Token Handling If the first linking worked but subsequent attempts fail: • Your server might mishandle refresh token requests. • Ensure your OAuth server supports the grant_type=refresh_token flow correctly.

Hey,

Hope you're keeping well.

Alexa doesn’t expose detailed account linking error logs directly, so most troubleshooting needs to happen on your OAuth provider side and in CloudWatch if your skill backend is on AWS. Make sure your authorization and token endpoints are publicly accessible over HTTPS and returning a valid JSON response with access_token, token_type, and expires_in fields. In the Alexa Developer Console, use the Test tab to reproduce the linking attempt, then check your backend logs in CloudWatch to see if the request from Alexa reached your service and where it failed.

Thanks and regards,
Taz