InvalidSlotTypeLiteral: Slot type “AMAZON.LITERAL” for slot “Text” in intent “RawText” is not...
AMAZON.LITERAL is deprecated as of October 22, 2018. Older skills built with AMAZON.LITERAL.
What is the alternative to AMAZON.LITERAL, I want each and every word spoken by user from Alexa device in my endpoint API.
I have created custom slots, but my endpoint is not called everytime.
Anyone have solution to this?
alexa alexa-skills-kit alexa-slot
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
add a comment |
AMAZON.LITERAL is deprecated as of October 22, 2018. Older skills built with AMAZON.LITERAL.
What is the alternative to AMAZON.LITERAL, I want each and every word spoken by user from Alexa device in my endpoint API.
I have created custom slots, but my endpoint is not called everytime.
Anyone have solution to this?
alexa alexa-skills-kit alexa-slot
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
add a comment |
AMAZON.LITERAL is deprecated as of October 22, 2018. Older skills built with AMAZON.LITERAL.
What is the alternative to AMAZON.LITERAL, I want each and every word spoken by user from Alexa device in my endpoint API.
I have created custom slots, but my endpoint is not called everytime.
Anyone have solution to this?
alexa alexa-skills-kit alexa-slot
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
AMAZON.LITERAL is deprecated as of October 22, 2018. Older skills built with AMAZON.LITERAL.
What is the alternative to AMAZON.LITERAL, I want each and every word spoken by user from Alexa device in my endpoint API.
I have created custom slots, but my endpoint is not called everytime.
Anyone have solution to this?
alexa alexa-skills-kit alexa-slot
alexa alexa-skills-kit alexa-slot
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
edited Nov 21 '18 at 12:14
Cicil Thomas
3,30521532
3,30521532
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
asked Nov 21 '18 at 11:57
Yash FatnaniYash Fatnani
1015
1015
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You will not get the entire user input through any inbuilt slots or intents. The closest one to your requirement that I can think of is AMAZON.SearchQuery.
AMAZON.SearchQuery
AMAZON.SearchQuery is a phrase-type slot that lets you capture less-predictable input that makes up the search query. You can use phrase slots when you cannot predict all possible values the user might say, or when there may not be an identifiable pattern that can be captured by a custom slot. The intended use of this slot is to capture short messages, comments, search queries, and other short free-form text, not the entire user spoken utterance.
Ex:
{
"intents": [
{
"name": "SearchIntent",
"slots": [
{
"name": "Query",
"type": "AMAZON.SearchQuery"
},
{
"name": "CityList",
"type": "AMAZON.US_CITY"
}
],
"samples": [
"search for {Query} near me",
"find out {Query}",
"search for {Query}",
"give me details about {CityList}"
]
}
]
}
You cannot add sample intent utterances consisting of only phrase type slots.
That means, you cannot give something like this:
{
"name": "QueryIntent",
"slots": [
{
"name": "query",
"type": "AMAZON.SearchQuery"
}
],
"samples": [
"{query}" // utterance with only phrase-type slot
]
}
More on AMAZON.SearchQuery here
Alexa will always will fire a POST request to your skill's endpoint with a payload whenever there is a user interaction.
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
|
show 4 more comments
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411545%2finvalidslottypeliteral-slot-type-amazon-literal-for-slot-text-in-intent-ra%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You will not get the entire user input through any inbuilt slots or intents. The closest one to your requirement that I can think of is AMAZON.SearchQuery.
AMAZON.SearchQuery
AMAZON.SearchQuery is a phrase-type slot that lets you capture less-predictable input that makes up the search query. You can use phrase slots when you cannot predict all possible values the user might say, or when there may not be an identifiable pattern that can be captured by a custom slot. The intended use of this slot is to capture short messages, comments, search queries, and other short free-form text, not the entire user spoken utterance.
Ex:
{
"intents": [
{
"name": "SearchIntent",
"slots": [
{
"name": "Query",
"type": "AMAZON.SearchQuery"
},
{
"name": "CityList",
"type": "AMAZON.US_CITY"
}
],
"samples": [
"search for {Query} near me",
"find out {Query}",
"search for {Query}",
"give me details about {CityList}"
]
}
]
}
You cannot add sample intent utterances consisting of only phrase type slots.
That means, you cannot give something like this:
{
"name": "QueryIntent",
"slots": [
{
"name": "query",
"type": "AMAZON.SearchQuery"
}
],
"samples": [
"{query}" // utterance with only phrase-type slot
]
}
More on AMAZON.SearchQuery here
Alexa will always will fire a POST request to your skill's endpoint with a payload whenever there is a user interaction.
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
|
show 4 more comments
You will not get the entire user input through any inbuilt slots or intents. The closest one to your requirement that I can think of is AMAZON.SearchQuery.
AMAZON.SearchQuery
AMAZON.SearchQuery is a phrase-type slot that lets you capture less-predictable input that makes up the search query. You can use phrase slots when you cannot predict all possible values the user might say, or when there may not be an identifiable pattern that can be captured by a custom slot. The intended use of this slot is to capture short messages, comments, search queries, and other short free-form text, not the entire user spoken utterance.
Ex:
{
"intents": [
{
"name": "SearchIntent",
"slots": [
{
"name": "Query",
"type": "AMAZON.SearchQuery"
},
{
"name": "CityList",
"type": "AMAZON.US_CITY"
}
],
"samples": [
"search for {Query} near me",
"find out {Query}",
"search for {Query}",
"give me details about {CityList}"
]
}
]
}
You cannot add sample intent utterances consisting of only phrase type slots.
That means, you cannot give something like this:
{
"name": "QueryIntent",
"slots": [
{
"name": "query",
"type": "AMAZON.SearchQuery"
}
],
"samples": [
"{query}" // utterance with only phrase-type slot
]
}
More on AMAZON.SearchQuery here
Alexa will always will fire a POST request to your skill's endpoint with a payload whenever there is a user interaction.
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
|
show 4 more comments
You will not get the entire user input through any inbuilt slots or intents. The closest one to your requirement that I can think of is AMAZON.SearchQuery.
AMAZON.SearchQuery
AMAZON.SearchQuery is a phrase-type slot that lets you capture less-predictable input that makes up the search query. You can use phrase slots when you cannot predict all possible values the user might say, or when there may not be an identifiable pattern that can be captured by a custom slot. The intended use of this slot is to capture short messages, comments, search queries, and other short free-form text, not the entire user spoken utterance.
Ex:
{
"intents": [
{
"name": "SearchIntent",
"slots": [
{
"name": "Query",
"type": "AMAZON.SearchQuery"
},
{
"name": "CityList",
"type": "AMAZON.US_CITY"
}
],
"samples": [
"search for {Query} near me",
"find out {Query}",
"search for {Query}",
"give me details about {CityList}"
]
}
]
}
You cannot add sample intent utterances consisting of only phrase type slots.
That means, you cannot give something like this:
{
"name": "QueryIntent",
"slots": [
{
"name": "query",
"type": "AMAZON.SearchQuery"
}
],
"samples": [
"{query}" // utterance with only phrase-type slot
]
}
More on AMAZON.SearchQuery here
Alexa will always will fire a POST request to your skill's endpoint with a payload whenever there is a user interaction.
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
You will not get the entire user input through any inbuilt slots or intents. The closest one to your requirement that I can think of is AMAZON.SearchQuery.
AMAZON.SearchQuery
AMAZON.SearchQuery is a phrase-type slot that lets you capture less-predictable input that makes up the search query. You can use phrase slots when you cannot predict all possible values the user might say, or when there may not be an identifiable pattern that can be captured by a custom slot. The intended use of this slot is to capture short messages, comments, search queries, and other short free-form text, not the entire user spoken utterance.
Ex:
{
"intents": [
{
"name": "SearchIntent",
"slots": [
{
"name": "Query",
"type": "AMAZON.SearchQuery"
},
{
"name": "CityList",
"type": "AMAZON.US_CITY"
}
],
"samples": [
"search for {Query} near me",
"find out {Query}",
"search for {Query}",
"give me details about {CityList}"
]
}
]
}
You cannot add sample intent utterances consisting of only phrase type slots.
That means, you cannot give something like this:
{
"name": "QueryIntent",
"slots": [
{
"name": "query",
"type": "AMAZON.SearchQuery"
}
],
"samples": [
"{query}" // utterance with only phrase-type slot
]
}
More on AMAZON.SearchQuery here
Alexa will always will fire a POST request to your skill's endpoint with a payload whenever there is a user interaction.
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
edited Nov 22 '18 at 8:10
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
answered Nov 21 '18 at 12:13
Cicil ThomasCicil Thomas
3,30521532
3,30521532
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
|
show 4 more comments
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
i am not getting value in my enpoint url "whatever user is speaking on alexa device"
– Yash Fatnani
Nov 21 '18 at 12:33
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
is your endpoint not called everytime or you are not getting any value from the request?
– Cicil Thomas
Nov 21 '18 at 12:34
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
its called only twice i am not getting query value. without value my api will not respond properly
– Yash Fatnani
Nov 21 '18 at 12:39
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
are you getting the query value in the request JSON while testing in test console
– Cicil Thomas
Nov 21 '18 at 12:45
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
request: { type: 'IntentRequest', requestId: 'amzn1.echo-api.request.a56d9c4a-a90a-4898-b12f-ecc9928a1ece', timestamp: '2018-11-21T13:21:10Z', locale: 'en-US', intent: { name: 'SearchIntent', confirmationStatus: 'NONE', slots: { Query: { name: 'Query', confirmationStatus: 'NONE' }, CityList: { name: 'CityList', confirmationStatus: 'NONE' } } } } } Their is no value in this request
– Yash Fatnani
Nov 21 '18 at 13:22
|
show 4 more comments
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53411545%2finvalidslottypeliteral-slot-type-amazon-literal-for-slot-text-in-intent-ra%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
