Before anything else, the Skill developer needs to register the Alexa Skill as an “App” with the API provider (e.g. Spotify). We call this step Alexa OAuth Provider Registration.
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
If you want to see the OAuth registration process in action, and look me over the shoulder while doing it, check out my video on OAuth Provider Registration.
Check out the other posts in this series on Alexa Account Linking:
- Part 0: Introduction to Account Linking via OAuth
- Part 1: Registration with OAuth Provider
- Part 2: Account Linking Configuration on Skill Interface
- Part 3: Skill Service: Get Access Token
- Part 4: Call Protected API from Skill Service
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 Alexa Book.
In the OAuth 2.0