Registration

After completing a standard AVS LWA authentication flow, your device must use its LWA token to register with AIA and establish a shared secret.

AIA and your device will use this shared secret for encrypting and decrypting messages on all AIA-specific MQTT topics, except for those involved in connection management.

• Getting Started
  • Protocol
  • AIA Envelope
• Request
  • Header
  • Body
• Success Response (HTTP 200)
  • HTTP Headers
  • Body
• Failure Response (HTTP 4xx and 5xx)
  • HTTP Headers
  • Body

Getting Started

Protocol

AIA exposes a secure HTTP/1.1 endpoint for registration mechanics.

Your device must be able to connect over HTTP/1.1 for initial registration, then use MQTT for remaining AIA-specific communication, including connection management, capability assertion, and exchanging messages on other topics required by Alexa capabilities.

Note: Your device must be able to follow HTTP/1.1 redirects.

AIA Envelope

Registration mechanics are part of v1 of the AIA envelope, indicated in the endpoint URI.

Request

Header

Header Parameters

Body

Sample Message

{
  "authentication": {
    "token": "{{STRING}}",
    "clientId": "{{STRING}}"
  },
  "encryption": {
    "algorithm": "{{STRING}}",
    "publicKey": "{{STRING}}"
  },
  "iot": {
    "awsAccountId": "{{STRING}}",
    "clientId": "{{STRING}}",
    "endpoint": "{{STRING}}"
  }
}

Parameters

Success Response (HTTP 200)

HTTP Headers

Header Parameters

Body

Sample Message

{
  "encryption": {
    "publicKey": "{{STRING}}"
  },
  "iot": {
    "topicRoot": "{{STRING}}"
  }
}

Parameters

Failure Response (HTTP 4xx and 5xx)

HTTP Headers

Header Parameters

Body

Sample Message

{
  "code": "{{STRING}}",
  "description": "{{STRING}}"
}

HTTP Response Codes and Body Parameters