Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Get started
Connect with Matter
Alexa Connect Kit
Add-ons
Certify
Resources
Skip to main content
You can configure your smart home add-on to support multiple languages. For each language, you update your add-on in the Alexa developer console and configure OAuth redirect URLs and regional Lambda endpoints. For more details, see Connect Your Device Cloud with Smart Home Add-ons and Steps to Build Smart Home Add-ons.

Steps to add language support

To support multiple languages in your add-on, complete the following steps:
  1. Verify interface language support.
  2. Add languages to your add-on in the developer console.
  3. Allow redirect URLs with your OAuth provider.
  4. Deploy your Lambda function to the required Amazon Web Services (AWS) regions.
  5. Send events to the correct Alexa endpoint.
  6. Configure regional Amazon Resource Name (ARN) endpoints.
  7. Test your add-on in each supported language.
  8. Provide language-specific distribution details for certification.

Verify language support

Language support varies by interface. Before you target a new language, verify that each interface that you implement in your add-on supports the new language. For details, see List of Alexa Interfaces and Supported Languages. A smart home add-on can support a single language or any combination of the following languages:
  • Arabic (SA)
  • Dutch (NL)
  • English (AU)
  • English (CA)
  • English (IN)
  • English (UK)
  • English (US)
  • French (CA)
  • French (FR)
  • German (DE)
  • Hindi (IN)
  • Italian (IT)
  • Japanese (JP)
  • Portuguese (BR)
  • Spanish (ES)
  • Spanish (MX)
  • Spanish (US)

Create multiple language versions of an add-on

You can add a language to an existing smart home add-on, or you can create a new add-on that supports multiple languages. To add a language to an existing add-on in the Alexa developer console
  1. Sign in to the Alexa developer console.
  2. On the Skills tab, under SKILL NAME, find the add-on that you want to update.
  3. Under ACTIONS, expand the dropdown list in your add-on’s row, and then select Edit.
  4. At the top of the sidebar, expand the language dropdown list, and then select Language settings.
  5. On the Language settings page, select + Add new Language, and then select the new languages your add-on supports.
  6. Configure the settings for each language. For more details, see Build Your Skill and Define Store Details for Publication.
To create a new add-on that supports one or more languages in the Alexa developer console
  1. Sign in to the Alexa developer console.
  2. On the Skills tab, choose Create Skill.
  3. On the Create a new skill page, provide the following information:
    1. For Skill name, enter a name for your add-on.
      You can configure language-specific names for the Alexa Skills Store in a later step.
    2. For Primary locale, choose a default language for your add-on.
    3. To continue, choose Next.
    4. For Choose a type of experience, select Smart Home.
    5. For Choose a model, select Smart Home.
    6. For Hosting services, select Provision your own.
    7. To continue, choose Next.
    8. Review your selections, and then at the top of the page, choose Create Skill.
  4. To add a new language and switch between languages, expand the language dropdown list, and then select Language settings.
  5. On the Language settings page, select + Add new Language, and then select the languages that your add-on supports.
  6. Configure the settings for each language on the Build and Distribution pages.

Allow additional redirect URLs with your OAuth provider

The account linking configuration you provide in the developer console is global across different language versions of your add-on. However, each AWS Lambda region for a multi-language add-on has a different redirect URL. To account-link your add-on to a device cloud and test your add-on, you must allow each redirect URL with your OAuth 2.0 provider. After you add one or more languages to your add-on, copy the redirect URLs in the developer console. For details, see Alexa Redirect URLs. To find the redirect URLs in the Alexa developer console
  1. Navigate back to your add-on in the developer console.
  2. On the Smart Home page, under 3. Account Linking, choose Setup Account Linking.
    Or, in the navigation pane, select ACCOUNT LINKING.
  3. Scroll down to Alexa Redirect URLs, and then copy the URLs.
  4. Add these URLs to your OAuth provider configuration.

Deploy your Lambda function to multiple regions

For each language your add-on supports, Alexa interprets the customer request and sends the correct directive to your add-on. You host your add-on code as an AWS Lambda function in the region closest to your customers. To support multiple locales, deploy your AWS Lambda function code to multiple AWS regions. For example, if your add-on supports English in the US and the UK, deploy your add-on code to both US East and EU regions. For detailed steps, see Add a Lambda function.

Locale-to-region mapping

The following table lists the AWS Lambda region and Alexa endpoint region for each supported language and locale. If the table doesn’t list a language or country, see Countries without native language support.
Add-on language and localeAWS Lambda regionAlexa endpoint region
Arabic (SA), English (CA), English (US), French (CA), Portuguese (BR), Spanish (MX), Spanish (US)US East (N. Virginia)North America
Dutch (NL), English (IN), English (UK), French (FR), German (DE), Hindi (IN), Italian (IT), Spanish (ES)Europe (Ireland)Europe and India
English (AU), Japanese (JP)US West (Oregon)Far East and Australia

Countries without native language support

You can publish your smart home add-on in a country even if Alexa doesn’t support the languages commonly spoken there. In these cases, customers interact with your add-on in a supported fallback language, typically English. To offer your add-on in a country without native language support, select the default add-on language, and then select the AWS Lambda and Alexa endpoint regions based on the country. The following table shows the supported languages and the AWS Lambda and Alexa endpoint regions by country.
CountrySupported add-on languagesAWS Lambda regionAlexa endpoint region
Argentina, Chile, Colombia, Costa Rica, PeruEnglish(US)US East (N. Virginia)North America
Belgium, Luxembourg, SwitzerlandFrench (FR), German (DE), Italian (IT)EU (Ireland)Europe and India
Denmark, Finland, Norway, Poland, Portugal, Sweden, TurkeyEnglish (US)US East (N. Virginia)North America
Indonesia, Malaysia, Philippines, Singapore, South KoreaEnglish (US)US East (N. Virginia)North America
Other countryEnglish (US)US East (N. Virginia)North America

Send events to the correct endpoint

If your add-on sends asynchronous responses or events, you must send them to the Alexa event gateway that corresponds to the AWS region where you host your Lambda function. The following table shows the Alexa event gateway endpoints by region.
  • North America: https://api.amazonalexa.com/v3/events
  • Europe and India: https://api.eu.amazonalexa.com/v3/events
  • Far East and Australia: https://api.fe.amazonalexa.com/v3/events

Provide the ARN numbers for your add-on in the developer console

To access the Lambda function that contains your add-on code, Alexa uses the Amazon Resource Name (ARN). The ARN defines the endpoint location of the Lambda function. To establish the link between Alexa and the Lambda function in each geographic region, you provide the ARN in the add-on configuration in the developer console. To configure a regional endpoint in the Alexa developer console
  1. Navigate back to your add-on in the developer console.
  2. On the Smart Home page, under 2. Smart Home service endpoint, choose the geographic regions that apply, for example, Europe, India.
  3. Enter the ARN for the Lambda endpoint in the text boxes provided.
    • If your add-on supports only one language or region, provide the same ARN for both the Default and the selected regional ARN.
    • If your add-on supports multiple languages or regions, provide the ARN for each region. Set one of the regional ARNs as the Default.
  4. Choose SAVE.

Test your add-on in multiple languages

Test your add-on with an account for each language you support. To test, you need cloud-connected devices that an Alexa-enabled device can discover. To find your add-on in the Alexa app, tap More, tap Skills & Games, and then tap Your Skills. Although Alexa handles language interpretation for you, test your add-on in all supported languages. Verify that your add-on responds correctly to utterances for each interface that it supports in the target language. Review the following common issues that might occur during multi-language testing:
  • Forgetting to allowlist OAuth redirect URLs for new regions
  • Deploying the Lambda function to the wrong AWS region
  • Sending events to the wrong Alexa event gateway endpoint
  • Missing ARN configuration for a regional endpoint in the developer console

Provide distribution details for each language

For each language your add-on supports, configure the settings on the Distribution page. Select the countries or regions where you plan to distribute your add-on. In the testing instructions, include test credentials for each language version. To pass certification, provide values for the following fields in each language you offer:
  • One-sentence description
  • Detailed description
  • Example phrases
  • Small and large icons
  • Keywords
  • Privacy questions
  • Testing instructions

Define add-on availability

Add-on availability applies to all languages that your add-on supports. You can choose the option to distribute your add-on in all countries where Amazon distributes add-ons, or you can choose specific countries and regions. You configure language and distribution independently. An add-on can be available in a particular country or region even if it doesn’t support languages commonly spoken there. Because a smart home add-on relies on cloud-connected devices, confirm that your devices are available and work correctly in each target country or region.
Last modified on November 13, 2026