Before anything else, the Skill developer needs to register the Alexa Skill as an “App” with the API provider (Spotify). Typically, there is a section on the developer portal of the API provider, as it is with Spotify. Here, a form needs to be completed.

In the course of this registration process, we need to provide a so-called redirect URL, redirect URI, or redirect endpoint. The Alexa Framework provides the redirect endpoint and its URL, we thus need to fill in the redirect URL values we get from the Skill Interface.

At the end of the process, we receive credentials for our Alexa Skill, called clientID and clientSecret. These values need to be provided as input to the account linking configuration on the Skill Interface. We also need to collect two URLs from the API provider: the authorization URL and the Token URL.

Check out the other posts in this series on Alexa Account Linking:

In my new book “Making Money with Alexa Skills – A Developer’s Guide” I describe not only how to develop, but also how to monetize Alexa Skills. Account linking is one of the possibilities for personalizing a Skill and make it unique – more practical approaches for personalizing Skills are described in the book.

In the OAuth 2.0 book you can find a simple and understandable explanation of all the standard OAuth Flows (such as those supported by Alexa). What makes this book unique is that the complicated OAuth interactions are visualized as easy-to-understand Sequence Diagrams.

Part 1 of Alexa Account Linking with OAuth: Registration with OAuth Provider

Also published on Medium.

Tagged on: