{ "version":"2.0", "metadata":{ "apiVersion":"2016-11-28", "endpointPrefix":"runtime.lex", "jsonVersion":"1.1", "protocol":"rest-json", "serviceFullName":"Amazon Lex Runtime Service", "serviceId":"Lex Runtime Service", "signatureVersion":"v4", "signingName":"lex", "uid":"runtime.lex-2016-11-28" }, "operations":{ "DeleteSession":{ "name":"DeleteSession", "http":{ "method":"DELETE", "requestUri":"/bot/{botName}/alias/{botAlias}/user/{userId}/session" }, "input":{"shape":"DeleteSessionRequest"}, "output":{"shape":"DeleteSessionResponse"}, "errors":[ {"shape":"NotFoundException"}, {"shape":"BadRequestException"}, {"shape":"LimitExceededException"}, {"shape":"InternalFailureException"}, {"shape":"ConflictException"} ], "documentation":"

Removes session information for a specified bot, alias, and user ID.

" }, "GetSession":{ "name":"GetSession", "http":{ "method":"GET", "requestUri":"/bot/{botName}/alias/{botAlias}/user/{userId}/session" }, "input":{"shape":"GetSessionRequest"}, "output":{"shape":"GetSessionResponse"}, "errors":[ {"shape":"NotFoundException"}, {"shape":"BadRequestException"}, {"shape":"LimitExceededException"}, {"shape":"InternalFailureException"} ], "documentation":"

Returns session information for a specified bot, alias, and user ID.

" }, "PostContent":{ "name":"PostContent", "http":{ "method":"POST", "requestUri":"/bot/{botName}/alias/{botAlias}/user/{userId}/content" }, "input":{"shape":"PostContentRequest"}, "output":{"shape":"PostContentResponse"}, "errors":[ {"shape":"NotFoundException"}, {"shape":"BadRequestException"}, {"shape":"LimitExceededException"}, {"shape":"InternalFailureException"}, {"shape":"ConflictException"}, {"shape":"UnsupportedMediaTypeException"}, {"shape":"NotAcceptableException"}, {"shape":"RequestTimeoutException"}, {"shape":"DependencyFailedException"}, {"shape":"BadGatewayException"}, {"shape":"LoopDetectedException"} ], "documentation":"

Sends user input (text or speech) to Amazon Lex. Clients use this API to send text and audio requests to Amazon Lex at runtime. Amazon Lex interprets the user input using the machine learning model that it built for the bot.

The PostContent operation supports audio input at 8kHz and 16kHz. You can use 8kHz audio to achieve higher speech recognition accuracy in telephone audio applications.

In response, Amazon Lex returns the next message to convey to the user. Consider the following example messages:

Not all Amazon Lex messages require a response from the user. For example, conclusion statements do not require a response. Some messages require only a yes or no response. In addition to the message, Amazon Lex provides additional context about the message in the response that you can use to enhance client behavior, such as displaying the appropriate client user interface. Consider the following examples:

In addition, Amazon Lex also returns your application-specific sessionAttributes. For more information, see Managing Conversation Context.

", "authtype":"v4-unsigned-body" }, "PostText":{ "name":"PostText", "http":{ "method":"POST", "requestUri":"/bot/{botName}/alias/{botAlias}/user/{userId}/text" }, "input":{"shape":"PostTextRequest"}, "output":{"shape":"PostTextResponse"}, "errors":[ {"shape":"NotFoundException"}, {"shape":"BadRequestException"}, {"shape":"LimitExceededException"}, {"shape":"InternalFailureException"}, {"shape":"ConflictException"}, {"shape":"DependencyFailedException"}, {"shape":"BadGatewayException"}, {"shape":"LoopDetectedException"} ], "documentation":"

Sends user input (text or SSML) to Amazon Lex. Client applications can use this API to send requests to Amazon Lex at runtime. Amazon Lex then interprets the user input using the machine learning model it built for the bot.

In response, Amazon Lex returns the next message to convey to the user an optional responseCard to display. Consider the following example messages:

Not all Amazon Lex messages require a user response. For example, a conclusion statement does not require a response. Some messages require only a \"yes\" or \"no\" user response. In addition to the message, Amazon Lex provides additional context about the message in the response that you might use to enhance client behavior, for example, to display the appropriate client user interface. These are the slotToElicit, dialogState, intentName, and slots fields in the response. Consider the following examples:

In addition, Amazon Lex also returns your application-specific sessionAttributes. For more information, see Managing Conversation Context.

" }, "PutSession":{ "name":"PutSession", "http":{ "method":"POST", "requestUri":"/bot/{botName}/alias/{botAlias}/user/{userId}/session" }, "input":{"shape":"PutSessionRequest"}, "output":{"shape":"PutSessionResponse"}, "errors":[ {"shape":"NotFoundException"}, {"shape":"BadRequestException"}, {"shape":"LimitExceededException"}, {"shape":"InternalFailureException"}, {"shape":"ConflictException"}, {"shape":"NotAcceptableException"}, {"shape":"DependencyFailedException"}, {"shape":"BadGatewayException"} ], "documentation":"

Creates a new session or modifies an existing session with an Amazon Lex bot. Use this operation to enable your application to set the state of the bot.

For more information, see Managing Sessions.

" } }, "shapes":{ "Accept":{"type":"string"}, "AttributesString":{ "type":"string", "sensitive":true }, "BadGatewayException":{ "type":"structure", "members":{ "Message":{"shape":"ErrorMessage"} }, "documentation":"

Either the Amazon Lex bot is still building, or one of the dependent services (Amazon Polly, AWS Lambda) failed with an internal service error.

", "error":{"httpStatusCode":502}, "exception":true }, "BadRequestException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

Request validation failed, there is no usable message in the context, or the bot build failed, is still in progress, or contains unbuilt changes.

", "error":{"httpStatusCode":400}, "exception":true }, "BlobStream":{ "type":"blob", "streaming":true }, "BotAlias":{"type":"string"}, "BotName":{"type":"string"}, "Button":{ "type":"structure", "required":[ "text", "value" ], "members":{ "text":{ "shape":"ButtonTextStringWithLength", "documentation":"

Text that is visible to the user on the button.

" }, "value":{ "shape":"ButtonValueStringWithLength", "documentation":"

The value sent to Amazon Lex when a user chooses the button. For example, consider button text \"NYC.\" When the user chooses the button, the value sent can be \"New York City.\"

" } }, "documentation":"

Represents an option to be shown on the client platform (Facebook, Slack, etc.)

" }, "ButtonTextStringWithLength":{ "type":"string", "max":15, "min":1 }, "ButtonValueStringWithLength":{ "type":"string", "max":1000, "min":1 }, "ConfirmationStatus":{ "type":"string", "enum":[ "None", "Confirmed", "Denied" ] }, "ConflictException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

Two clients are using the same AWS account, Amazon Lex bot, and user ID.

", "error":{"httpStatusCode":409}, "exception":true }, "ContentType":{ "type":"string", "enum":["application/vnd.amazonaws.card.generic"] }, "DeleteSessionRequest":{ "type":"structure", "required":[ "botName", "botAlias", "userId" ], "members":{ "botName":{ "shape":"BotName", "documentation":"

The name of the bot that contains the session data.

", "location":"uri", "locationName":"botName" }, "botAlias":{ "shape":"BotAlias", "documentation":"

The alias in use for the bot that contains the session data.

", "location":"uri", "locationName":"botAlias" }, "userId":{ "shape":"UserId", "documentation":"

The identifier of the user associated with the session data.

", "location":"uri", "locationName":"userId" } } }, "DeleteSessionResponse":{ "type":"structure", "members":{ "botName":{ "shape":"BotName", "documentation":"

The name of the bot associated with the session data.

" }, "botAlias":{ "shape":"BotAlias", "documentation":"

The alias in use for the bot associated with the session data.

" }, "userId":{ "shape":"UserId", "documentation":"

The ID of the client application user.

" }, "sessionId":{ "shape":"String", "documentation":"

The unique identifier for the session.

" } } }, "DependencyFailedException":{ "type":"structure", "members":{ "Message":{"shape":"ErrorMessage"} }, "documentation":"

One of the dependencies, such as AWS Lambda or Amazon Polly, threw an exception. For example,

", "error":{"httpStatusCode":424}, "exception":true }, "DialogAction":{ "type":"structure", "required":["type"], "members":{ "type":{ "shape":"DialogActionType", "documentation":"

The next action that the bot should take in its interaction with the user. The possible values are:

" }, "intentName":{ "shape":"IntentName", "documentation":"

The name of the intent.

" }, "slots":{ "shape":"StringMap", "documentation":"

Map of the slots that have been gathered and their values.

" }, "slotToElicit":{ "shape":"String", "documentation":"

The name of the slot that should be elicited from the user.

" }, "fulfillmentState":{ "shape":"FulfillmentState", "documentation":"

The fulfillment state of the intent. The possible values are:

" }, "message":{ "shape":"Text", "documentation":"

The message that should be shown to the user. If you don't specify a message, Amazon Lex will use the message configured for the intent.

" }, "messageFormat":{ "shape":"MessageFormatType", "documentation":"" } }, "documentation":"

Describes the next action that the bot should take in its interaction with the user and provides information about the context in which the action takes place. Use the DialogAction data type to set the interaction to a specific state, or to return the interaction to a previous state.

" }, "DialogActionType":{ "type":"string", "enum":[ "ElicitIntent", "ConfirmIntent", "ElicitSlot", "Close", "Delegate" ] }, "DialogState":{ "type":"string", "enum":[ "ElicitIntent", "ConfirmIntent", "ElicitSlot", "Fulfilled", "ReadyForFulfillment", "Failed" ] }, "ErrorMessage":{"type":"string"}, "FulfillmentState":{ "type":"string", "enum":[ "Fulfilled", "Failed", "ReadyForFulfillment" ] }, "GenericAttachment":{ "type":"structure", "members":{ "title":{ "shape":"StringWithLength", "documentation":"

The title of the option.

" }, "subTitle":{ "shape":"StringWithLength", "documentation":"

The subtitle shown below the title.

" }, "attachmentLinkUrl":{ "shape":"StringUrlWithLength", "documentation":"

The URL of an attachment to the response card.

" }, "imageUrl":{ "shape":"StringUrlWithLength", "documentation":"

The URL of an image that is displayed to the user.

" }, "buttons":{ "shape":"listOfButtons", "documentation":"

The list of options to show to the user.

" } }, "documentation":"

Represents an option rendered to the user when a prompt is shown. It could be an image, a button, a link, or text.

" }, "GetSessionRequest":{ "type":"structure", "required":[ "botName", "botAlias", "userId" ], "members":{ "botName":{ "shape":"BotName", "documentation":"

The name of the bot that contains the session data.

", "location":"uri", "locationName":"botName" }, "botAlias":{ "shape":"BotAlias", "documentation":"

The alias in use for the bot that contains the session data.

", "location":"uri", "locationName":"botAlias" }, "userId":{ "shape":"UserId", "documentation":"

The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot.

", "location":"uri", "locationName":"userId" } } }, "GetSessionResponse":{ "type":"structure", "members":{ "recentIntentSummaryView":{ "shape":"IntentSummaryList", "documentation":"

An array of information about the intents used in the session. The array can contain a maximum of three summaries. If more than three intents are used in the session, the recentIntentSummaryView operation contains information about the last three intents used.

" }, "sessionAttributes":{ "shape":"StringMap", "documentation":"

Map of key/value pairs representing the session-specific context information. It contains application information passed between Amazon Lex and a client application.

" }, "sessionId":{ "shape":"String", "documentation":"

A unique identifier for the session.

" }, "dialogAction":{ "shape":"DialogAction", "documentation":"

Describes the current state of the bot.

" } } }, "HttpContentType":{"type":"string"}, "IntentName":{"type":"string"}, "IntentSummary":{ "type":"structure", "required":["dialogActionType"], "members":{ "intentName":{ "shape":"IntentName", "documentation":"

The name of the intent.

" }, "slots":{ "shape":"StringMap", "documentation":"

Map of the slots that have been gathered and their values.

" }, "confirmationStatus":{ "shape":"ConfirmationStatus", "documentation":"

The status of the intent after the user responds to the confirmation prompt. If the user confirms the intent, Amazon Lex sets this field to Confirmed. If the user denies the intent, Amazon Lex sets this value to Denied. The possible values are:

" }, "dialogActionType":{ "shape":"DialogActionType", "documentation":"

The next action that the bot should take in its interaction with the user. The possible values are:

" }, "fulfillmentState":{ "shape":"FulfillmentState", "documentation":"

The fulfillment state of the intent. The possible values are:

" }, "slotToElicit":{ "shape":"String", "documentation":"

The next slot to elicit from the user. If there is not slot to elicit, the field is blank.

" } }, "documentation":"

Provides information about the state of an intent. You can use this information to get the current state of an intent so that you can process the intent, or so that you can return the intent to its previous state.

" }, "IntentSummaryList":{ "type":"list", "member":{"shape":"IntentSummary"}, "max":3, "min":0 }, "InternalFailureException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

Internal service error. Retry the call.

", "error":{"httpStatusCode":500}, "exception":true, "fault":true }, "LimitExceededException":{ "type":"structure", "members":{ "retryAfterSeconds":{ "shape":"String", "location":"header", "locationName":"Retry-After" }, "message":{"shape":"String"} }, "documentation":"

Exceeded a limit.

", "error":{"httpStatusCode":429}, "exception":true }, "LoopDetectedException":{ "type":"structure", "members":{ "Message":{"shape":"ErrorMessage"} }, "documentation":"

This exception is not used.

", "error":{"httpStatusCode":508}, "exception":true }, "MessageFormatType":{ "type":"string", "enum":[ "PlainText", "CustomPayload", "SSML", "Composite" ] }, "NotAcceptableException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

The accept header in the request does not have a valid value.

", "error":{"httpStatusCode":406}, "exception":true }, "NotFoundException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

The resource (such as the Amazon Lex bot or an alias) that is referred to is not found.

", "error":{"httpStatusCode":404}, "exception":true }, "PostContentRequest":{ "type":"structure", "required":[ "botName", "botAlias", "userId", "contentType", "inputStream" ], "members":{ "botName":{ "shape":"BotName", "documentation":"

Name of the Amazon Lex bot.

", "location":"uri", "locationName":"botName" }, "botAlias":{ "shape":"BotAlias", "documentation":"

Alias of the Amazon Lex bot.

", "location":"uri", "locationName":"botAlias" }, "userId":{ "shape":"UserId", "documentation":"

The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At runtime, each request must contain the userID field.

To decide the user ID to use for your application, consider the following factors.

", "location":"uri", "locationName":"userId" }, "sessionAttributes":{ "shape":"AttributesString", "documentation":"

You pass this value as the x-amz-lex-session-attributes HTTP header.

Application-specific information passed between Amazon Lex and a client application. The value must be a JSON serialized and base64 encoded map with string keys and values. The total size of the sessionAttributes and requestAttributes headers is limited to 12 KB.

For more information, see Setting Session Attributes.

", "jsonvalue":true, "location":"header", "locationName":"x-amz-lex-session-attributes" }, "requestAttributes":{ "shape":"AttributesString", "documentation":"

You pass this value as the x-amz-lex-request-attributes HTTP header.

Request-specific information passed between Amazon Lex and a client application. The value must be a JSON serialized and base64 encoded map with string keys and values. The total size of the requestAttributes and sessionAttributes headers is limited to 12 KB.

The namespace x-amz-lex: is reserved for special attributes. Don't create any request attributes with the prefix x-amz-lex:.

For more information, see Setting Request Attributes.

", "jsonvalue":true, "location":"header", "locationName":"x-amz-lex-request-attributes" }, "contentType":{ "shape":"HttpContentType", "documentation":"

You pass this value as the Content-Type HTTP header.

Indicates the audio format or text. The header value must start with one of the following prefixes:

", "location":"header", "locationName":"Content-Type" }, "accept":{ "shape":"Accept", "documentation":"

You pass this value as the Accept HTTP header.

The message Amazon Lex returns in the response can be either text or speech based on the Accept HTTP header value in the request.

", "location":"header", "locationName":"Accept" }, "inputStream":{ "shape":"BlobStream", "documentation":"

User input in PCM or Opus audio format or text format as described in the Content-Type HTTP header.

You can stream audio data to Amazon Lex or you can create a local buffer that captures all of the audio data before sending. In general, you get better performance if you stream audio data rather than buffering the data locally.

" } }, "payload":"inputStream" }, "PostContentResponse":{ "type":"structure", "members":{ "contentType":{ "shape":"HttpContentType", "documentation":"

Content type as specified in the Accept HTTP header in the request.

", "location":"header", "locationName":"Content-Type" }, "intentName":{ "shape":"IntentName", "documentation":"

Current user intent that Amazon Lex is aware of.

", "location":"header", "locationName":"x-amz-lex-intent-name" }, "slots":{ "shape":"String", "documentation":"

Map of zero or more intent slots (name/value pairs) Amazon Lex detected from the user input during the conversation. The field is base-64 encoded.

Amazon Lex creates a resolution list containing likely values for a slot. The value that it returns is determined by the valueSelectionStrategy selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUE, the value provided by the user is returned, if the user value is similar to the slot values. If valueSelectionStrategy is set to TOP_RESOLUTION Amazon Lex returns the first value in the resolution list or, if there is no resolution list, null. If you don't specify a valueSelectionStrategy, the default is ORIGINAL_VALUE.

", "jsonvalue":true, "location":"header", "locationName":"x-amz-lex-slots" }, "sessionAttributes":{ "shape":"String", "documentation":"

Map of key/value pairs representing the session-specific context information.

", "jsonvalue":true, "location":"header", "locationName":"x-amz-lex-session-attributes" }, "message":{ "shape":"Text", "documentation":"

The message to convey to the user. The message can come from the bot's configuration or from a Lambda function.

If the intent is not configured with a Lambda function, or if the Lambda function returned Delegate as the dialogAction.type in its response, Amazon Lex decides on the next course of action and selects an appropriate message from the bot's configuration based on the current interaction context. For example, if Amazon Lex isn't able to understand user input, it uses a clarification prompt message.

When you create an intent you can assign messages to groups. When messages are assigned to groups Amazon Lex returns one message from each group in the response. The message field is an escaped JSON string containing the messages. For more information about the structure of the JSON string returned, see msg-prompts-formats.

If the Lambda function returns a message, Amazon Lex passes it to the client in its response.

", "location":"header", "locationName":"x-amz-lex-message" }, "messageFormat":{ "shape":"MessageFormatType", "documentation":"

The format of the response message. One of the following values:

", "location":"header", "locationName":"x-amz-lex-message-format" }, "dialogState":{ "shape":"DialogState", "documentation":"

Identifies the current state of the user interaction. Amazon Lex returns one of the following values as dialogState. The client can optionally use this information to customize the user interface.

", "location":"header", "locationName":"x-amz-lex-dialog-state" }, "slotToElicit":{ "shape":"String", "documentation":"

If the dialogState value is ElicitSlot, returns the name of the slot for which Amazon Lex is eliciting a value.

", "location":"header", "locationName":"x-amz-lex-slot-to-elicit" }, "inputTranscript":{ "shape":"String", "documentation":"

The text used to process the request.

If the input was an audio stream, the inputTranscript field contains the text extracted from the audio stream. This is the text that is actually processed to recognize intents and slot values. You can use this information to determine if Amazon Lex is correctly processing the audio that you send.

", "location":"header", "locationName":"x-amz-lex-input-transcript" }, "audioStream":{ "shape":"BlobStream", "documentation":"

The prompt (or statement) to convey to the user. This is based on the bot configuration and context. For example, if Amazon Lex did not understand the user intent, it sends the clarificationPrompt configured for the bot. If the intent requires confirmation before taking the fulfillment action, it sends the confirmationPrompt. Another example: Suppose that the Lambda function successfully fulfilled the intent, and sent a message to convey to the user. Then Amazon Lex sends that message in the response.

" } }, "payload":"audioStream" }, "PostTextRequest":{ "type":"structure", "required":[ "botName", "botAlias", "userId", "inputText" ], "members":{ "botName":{ "shape":"BotName", "documentation":"

The name of the Amazon Lex bot.

", "location":"uri", "locationName":"botName" }, "botAlias":{ "shape":"BotAlias", "documentation":"

The alias of the Amazon Lex bot.

", "location":"uri", "locationName":"botAlias" }, "userId":{ "shape":"UserId", "documentation":"

The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot. At runtime, each request must contain the userID field.

To decide the user ID to use for your application, consider the following factors.

", "location":"uri", "locationName":"userId" }, "sessionAttributes":{ "shape":"StringMap", "documentation":"

Application-specific information passed between Amazon Lex and a client application.

For more information, see Setting Session Attributes.

" }, "requestAttributes":{ "shape":"StringMap", "documentation":"

Request-specific information passed between Amazon Lex and a client application.

The namespace x-amz-lex: is reserved for special attributes. Don't create any request attributes with the prefix x-amz-lex:.

For more information, see Setting Request Attributes.

" }, "inputText":{ "shape":"Text", "documentation":"

The text that the user entered (Amazon Lex interprets this text).

" } } }, "PostTextResponse":{ "type":"structure", "members":{ "intentName":{ "shape":"IntentName", "documentation":"

The current user intent that Amazon Lex is aware of.

" }, "slots":{ "shape":"StringMap", "documentation":"

The intent slots that Amazon Lex detected from the user input in the conversation.

Amazon Lex creates a resolution list containing likely values for a slot. The value that it returns is determined by the valueSelectionStrategy selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUE, the value provided by the user is returned, if the user value is similar to the slot values. If valueSelectionStrategy is set to TOP_RESOLUTION Amazon Lex returns the first value in the resolution list or, if there is no resolution list, null. If you don't specify a valueSelectionStrategy, the default is ORIGINAL_VALUE.

" }, "sessionAttributes":{ "shape":"StringMap", "documentation":"

A map of key-value pairs representing the session-specific context information.

" }, "message":{ "shape":"Text", "documentation":"

The message to convey to the user. The message can come from the bot's configuration or from a Lambda function.

If the intent is not configured with a Lambda function, or if the Lambda function returned Delegate as the dialogAction.type its response, Amazon Lex decides on the next course of action and selects an appropriate message from the bot's configuration based on the current interaction context. For example, if Amazon Lex isn't able to understand user input, it uses a clarification prompt message.

When you create an intent you can assign messages to groups. When messages are assigned to groups Amazon Lex returns one message from each group in the response. The message field is an escaped JSON string containing the messages. For more information about the structure of the JSON string returned, see msg-prompts-formats.

If the Lambda function returns a message, Amazon Lex passes it to the client in its response.

" }, "messageFormat":{ "shape":"MessageFormatType", "documentation":"

The format of the response message. One of the following values:

" }, "dialogState":{ "shape":"DialogState", "documentation":"

Identifies the current state of the user interaction. Amazon Lex returns one of the following values as dialogState. The client can optionally use this information to customize the user interface.

" }, "slotToElicit":{ "shape":"String", "documentation":"

If the dialogState value is ElicitSlot, returns the name of the slot for which Amazon Lex is eliciting a value.

" }, "responseCard":{ "shape":"ResponseCard", "documentation":"

Represents the options that the user has to respond to the current prompt. Response Card can come from the bot configuration (in the Amazon Lex console, choose the settings button next to a slot) or from a code hook (Lambda function).

" } } }, "PutSessionRequest":{ "type":"structure", "required":[ "botName", "botAlias", "userId" ], "members":{ "botName":{ "shape":"BotName", "documentation":"

The name of the bot that contains the session data.

", "location":"uri", "locationName":"botName" }, "botAlias":{ "shape":"BotAlias", "documentation":"

The alias in use for the bot that contains the session data.

", "location":"uri", "locationName":"botAlias" }, "userId":{ "shape":"UserId", "documentation":"

The ID of the client application user. Amazon Lex uses this to identify a user's conversation with your bot.

", "location":"uri", "locationName":"userId" }, "sessionAttributes":{ "shape":"StringMap", "documentation":"

Map of key/value pairs representing the session-specific context information. It contains application information passed between Amazon Lex and a client application.

" }, "dialogAction":{ "shape":"DialogAction", "documentation":"

Sets the next action that the bot should take to fulfill the conversation.

" }, "accept":{ "shape":"Accept", "documentation":"

The message that Amazon Lex returns in the response can be either text or speech based depending on the value of this field.

", "location":"header", "locationName":"Accept" } } }, "PutSessionResponse":{ "type":"structure", "members":{ "contentType":{ "shape":"HttpContentType", "documentation":"

Content type as specified in the Accept HTTP header in the request.

", "location":"header", "locationName":"Content-Type" }, "intentName":{ "shape":"IntentName", "documentation":"

The name of the current intent.

", "location":"header", "locationName":"x-amz-lex-intent-name" }, "slots":{ "shape":"String", "documentation":"

Map of zero or more intent slots Amazon Lex detected from the user input during the conversation.

Amazon Lex creates a resolution list containing likely values for a slot. The value that it returns is determined by the valueSelectionStrategy selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUE, the value provided by the user is returned, if the user value is similar to the slot values. If valueSelectionStrategy is set to TOP_RESOLUTION Amazon Lex returns the first value in the resolution list or, if there is no resolution list, null. If you don't specify a valueSelectionStrategy the default is ORIGINAL_VALUE.

", "jsonvalue":true, "location":"header", "locationName":"x-amz-lex-slots" }, "sessionAttributes":{ "shape":"String", "documentation":"

Map of key/value pairs representing session-specific context information.

", "jsonvalue":true, "location":"header", "locationName":"x-amz-lex-session-attributes" }, "message":{ "shape":"Text", "documentation":"

The next message that should be presented to the user.

", "location":"header", "locationName":"x-amz-lex-message" }, "messageFormat":{ "shape":"MessageFormatType", "documentation":"

The format of the response message. One of the following values:

", "location":"header", "locationName":"x-amz-lex-message-format" }, "dialogState":{ "shape":"DialogState", "documentation":"

", "location":"header", "locationName":"x-amz-lex-dialog-state" }, "slotToElicit":{ "shape":"String", "documentation":"

If the dialogState is ElicitSlot, returns the name of the slot for which Amazon Lex is eliciting a value.

", "location":"header", "locationName":"x-amz-lex-slot-to-elicit" }, "audioStream":{ "shape":"BlobStream", "documentation":"

The audio version of the message to convey to the user.

" }, "sessionId":{ "shape":"String", "documentation":"

A unique identifier for the session.

", "location":"header", "locationName":"x-amz-lex-session-id" } }, "payload":"audioStream" }, "RequestTimeoutException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

The input speech is too long.

", "error":{"httpStatusCode":408}, "exception":true }, "ResponseCard":{ "type":"structure", "members":{ "version":{ "shape":"String", "documentation":"

The version of the response card format.

" }, "contentType":{ "shape":"ContentType", "documentation":"

The content type of the response.

" }, "genericAttachments":{ "shape":"genericAttachmentList", "documentation":"

An array of attachment objects representing options.

" } }, "documentation":"

If you configure a response card when creating your bots, Amazon Lex substitutes the session attributes and slot values that are available, and then returns it. The response card can also come from a Lambda function ( dialogCodeHook and fulfillmentActivity on an intent).

" }, "String":{"type":"string"}, "StringMap":{ "type":"map", "key":{"shape":"String"}, "value":{"shape":"String"}, "sensitive":true }, "StringUrlWithLength":{ "type":"string", "max":2048, "min":1 }, "StringWithLength":{ "type":"string", "max":80, "min":1 }, "Text":{ "type":"string", "max":1024, "min":1, "sensitive":true }, "UnsupportedMediaTypeException":{ "type":"structure", "members":{ "message":{"shape":"String"} }, "documentation":"

The Content-Type header (PostContent API) has an invalid value.

", "error":{"httpStatusCode":415}, "exception":true }, "UserId":{ "type":"string", "max":100, "min":2, "pattern":"[0-9a-zA-Z._:-]+" }, "genericAttachmentList":{ "type":"list", "member":{"shape":"GenericAttachment"}, "max":10, "min":0 }, "listOfButtons":{ "type":"list", "member":{"shape":"Button"}, "max":5, "min":0 } }, "documentation":"

Amazon Lex provides both build and runtime endpoints. Each endpoint provides a set of operations (API). Your conversational bot uses the runtime API to understand user utterances (user input text or voice). For example, suppose a user says \"I want pizza\", your bot sends this input to Amazon Lex using the runtime API. Amazon Lex recognizes that the user request is for the OrderPizza intent (one of the intents defined in the bot). Then Amazon Lex engages in user conversation on behalf of the bot to elicit required information (slot values, such as pizza size and crust type), and then performs fulfillment activity (that you configured when you created the bot). You use the build-time API to create and manage your Amazon Lex bot. For a list of build-time operations, see the build-time API, .

" }