Alexa.Authorization interface in your Alexa add-on to give your add-on access to the Alexa event gateway. Access to the gateway enables you to send asynchronous responses and proactive events, such as Alexa.ChangeReport, to Alexa.
For the definitions of the message properties, see Alexa Interface Message and Property Reference.
Event gateway authorization
The purpose of theAlexa.Authorization.AcceptGrant directive is to enable you to obtain credentials that identify and authenticate a customer to Alexa.
Alexa sends an AcceptGrant directive after a customer enables a smart home add-on and goes through the account linking process, or when you update an existing smart home add-on to support proactive events.
The AcceptGrant directive contains the following information:
- Alexa sends you an authorization code. Exchange the authorization code for an access token and refresh token by using Login With Amazon (LWA). For details, see the Get access token with authorization code operation and LWA Authorization Code Grant.
- Alexa sends you the access token for the customer that Alexa received during the account linking process. Store the token, and use the token to identify the customer in your system.
Directives
TheAlexa.Authorization interface defines the following directives.
AcceptGrant directive
Support theAcceptGrant directive so that you can obtain and store credentials that identify a customer to Alexa.
AcceptGrant directive example
The following example illustrates anAcceptGrant directive that Alexa sends to your add-on. Because this interface is synchronous, the message doesn’t contain a correlation token.
AcceptGrant directive payload
The following table shows the payload details for theAcceptGrant directive.
| Property | Description | Type | Required |
|---|---|---|---|
grant | Information that identifies a customer in Amazon Alexa systems. | Object | Yes |
grant.type | Type of grant. Valid value: OAuth2.AuthorizationCode. | String | Yes |
grant.code | Authorization code for the customer. Exchange the authorization code for an access token and refresh token by using the Login With Amazon (LWA) OAuth 2.0 server. | String | Yes |
grantee | Information that identifies a customer in the linked-account service or system. | Object | Yes |
grantee.type | Type of access token. Smart home add-ons support bearer token types only. For more details, see OAuth Access Token Types. Valid value: BearerToken. | String | Yes |
grantee.token | The customer access token received by Alexa during the account linking process. | String | Yes |
AcceptGrant response
If you handle anAcceptGrant directive successfully, respond with an AcceptGrant.Response. Because this interface is synchronous only, don’t include a correlation token.
The following example shows an AcceptGrant.Response. The response doesn’t require a payload.
AcceptGrant error handling
If you can’t handle anAcceptGrant directive successfully for one of the following reasons, respond with an Alexa.Authorization.ErrorResponse:
- You’re unable to call LWA to exchange the authorization code for access and refresh tokens.
- You’re unable to store the access and refresh tokens for the customer.
- Any other error that occurs while you try to retrieve and store the access and refresh tokens.
Alexa.Authorization.ErrorResponse.

