We are excited to announce the addition of the Intent Request History API to the Alexa Skill Management API (SMAPI) and the Alexa Skills Kit Command-Line Interface (ASK CLI). The Intent Request History API enables you to improve the customer experience by understanding how customers are engaging with your Alexa skill. This API offers an aggregated and anonymized view of intent requests from the last 30 days for skills that meet a minimum threshold of customer engagement.
As part of your query to the Intent Request History API, you can filter by intents, confidence level (high, medium, or low), and several other characteristics via SMAPI or ASK CLI. You can analyze the data in several ways:
- Detect anomalies where natural language understanding (NLU) has mapped a request to the wrong intent with high confidence, or conversely, to the right intent with low confidence, resulting in the request not sent to the skill
- Use the data to guide you to update your skill’s sample utterances and slots in a customer-friendly manner
- Identify missing use cases that you may want to include in your skill
- Identify popular slot values in different locales
- Identify possible new dialogs for your skill
To construct your query via SMAPI, see Intent Request History API. To create your query using ASK CLI, see Alexa Skill Kits CLI Command Reference. Each listed item is unique, although more than one customer may have used it. You can use a simple query in ASK CLI (shown below), where the skill-id is in the format "amzn1.ask.skill.12345678-1234-1234-123456789123".
ask api intent-requests-history --skill-id <skill-id>
Build Engaging Skills, Earn Money with Alexa Developer Rewards
Every month, developers can earn money for eligible skills that drive some of the highest customer engagement. Developers can increase their level of skill engagement and potentially earn more by improving their skill, building more skills, and making their skills available in the US, UK, and Germany. Learn more about our rewards program and start building today.
Source: Alexa Developer Blog