!^Wm      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijkl(c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)None27_4  (c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)None"#272ramazonka-lex-runtimeIf 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).See:  smart constructor.amazonka-lex-runtimerRepresents an option rendered to the user when a prompt is shown. It could be an image, a button, a link, or text.See:  smart constructor.amazonka-lex-runtimeORepresents an option to be shown on the client platform (Facebook, Slack, etc.)See:  smart constructor.amazonka-lex-runtimeCreates a value of 4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired:2 - Text that is visible to the user on the button. - 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."amazonka-lex-runtime/Text that is visible to the user on the button.amazonka-lex-runtimeThe 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."amazonka-lex-runtimeCreates a value of 4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired:+ - The list of options to show to the user.& - The subtitle shown below the title.5 - The URL of an image that is displayed to the user.1 - The URL of an attachment to the response card. - The title of the option.amazonka-lex-runtime(The list of options to show to the user.amazonka-lex-runtime#The subtitle shown below the title.amazonka-lex-runtime2The URL of an image that is displayed to the user.amazonka-lex-runtime.The URL of an attachment to the response card.amazonka-lex-runtimeThe title of the option.amazonka-lex-runtimeCreates a value of 4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired:7 - An array of attachment objects representing options.+ - The version of the response card format.$ - The content type of the response.amazonka-lex-runtime4An array of attachment objects representing options.amazonka-lex-runtime(The version of the response card format.amazonka-lex-runtime!The content type of the response.amazonka-lex-runtimeamazonka-lex-runtimemnopqrstuvwxy(c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)NoneJ amazonka-lex-runtime API version  2016-11-285 of the Amazon Lex Runtime Service SDK configuration.amazonka-lex-runtime=The accept header in the request does not have a valid value. amazonka-lex-runtime]One of the dependencies, such as AWS Lambda or Amazon Polly, threw an exception. For example,MIf Amazon Lex does not have sufficient permissions to call a Lambda function.=If a Lambda function takes longer than 30 seconds to execute.+If a fulfillment Lambda function returns a Delegate0 dialog action without removing any slot values.!amazonka-lex-runtimeThe Content-Type header ( PostContent API) has an invalid value."amazonka-lex-runtimeHTwo clients are using the same AWS account, Amazon Lex bot, and user ID.#amazonka-lex-runtimeWThe resource (such as the Amazon Lex bot or an alias) that is referred to is not found.$amazonka-lex-runtimeThe input speech is too long.%amazonka-lex-runtimeThis exception is not used.&amazonka-lex-runtime'Internal service error. Retry the call.'amazonka-lex-runtimeEither the Amazon Lex bot is still building, or one of the dependent services (Amazon Polly, AWS Lambda) failed with an internal service error.(amazonka-lex-runtimeRequest validation failed, there is no usable message in the context, or the bot build failed, is still in progress, or contains unbuilt changes.)amazonka-lex-runtimeExceeded a limit.*  !"#$%&'()* !"#$%&'()  (c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)None "#27HV *amazonka-lex-runtimeSee: 3 smart constructor.+amazonka-lex-runtimeSee: , smart constructor.,amazonka-lex-runtimeCreates a value of +4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired:-b - Request-specific information passed between Amazon Lex and a client application. The namespace  x-amz-lex:Y is reserved for special attributes. Don't create any request attributes with the prefix  x-amz-lex: . For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribsSetting Request Attributes ..r - Application-specific information passed between Amazon Lex and a client application. For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribsSetting Session Attributes ./" - The name of the Amazon Lex bot.0# - The alias of the Amazon Lex bot.1 - 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 userIDe field. To decide the user ID to use for your application, consider the following factors. * The userID7 field must not contain any personally identifiable information of the user, for example, name, personal identification numbers, or other end user personal information. * If you want a user to start a conversation on one device and continue on another device, use a user-specific identifier. * If you want the same user to be able to have two independent conversations on two different devices, choose a device-specific identifier. * A user can't have two independent conversations with two different versions of the same bot. For example, a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will need to have conversation with two different versions, for example, while testing, include the bot alias in the user ID to separate the two conversations.2D - The text that the user entered (Amazon Lex interprets this text).-amazonka-lex-runtime_Request-specific information passed between Amazon Lex and a client application. The namespace  x-amz-lex:Y is reserved for special attributes. Don't create any request attributes with the prefix  x-amz-lex: . For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribsSetting Request Attributes ..amazonka-lex-runtimeoApplication-specific information passed between Amazon Lex and a client application. For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribsSetting Session Attributes ./amazonka-lex-runtimeThe name of the Amazon Lex bot.0amazonka-lex-runtime The alias of the Amazon Lex bot.1amazonka-lex-runtimeThe 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 userIDe field. To decide the user ID to use for your application, consider the following factors. * The userID7 field must not contain any personally identifiable information of the user, for example, name, personal identification numbers, or other end user personal information. * If you want a user to start a conversation on one device and continue on another device, use a user-specific identifier. * If you want the same user to be able to have two independent conversations on two different devices, choose a device-specific identifier. * A user can't have two independent conversations with two different versions of the same bot. For example, a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will need to have conversation with two different versions, for example, while testing, include the bot alias in the user ID to separate the two conversations.2amazonka-lex-runtimeAThe text that the user entered (Amazon Lex interprets this text).3amazonka-lex-runtimeCreates a value of *4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired: 4 - 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 valueSelectionStrategy8 selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUEc , 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 .5 - 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).67 - The current user intent that Amazon Lex is aware of.7k - Identifies the current state of the user interaction. Amazon Lex returns one of the following values as  dialogStateZ . The client can optionally use this information to customize the user interface. *  ElicitIntent - Amazon Lex wants to elicit user intent. For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState. *  ConfirmIntent - Amazon Lex is expecting a "yes" or "no" response. For example, Amazon Lex wants user confirmation before fulfilling an intent. Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink). *  ElicitSlot - Amazon Lex is expecting a slot value for the current intent. For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately. *  Fulfilledl - Conveys that the Lambda function configured for the intent has successfully fulfilled the intent. * ReadyForFulfillment= - Conveys that the client has to fulfill the intent. * FailedF - Conveys that the conversation with the user failed. This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.8J - The format of the response message. One of the following values: *  PlainText0 - The message contains plain UTF-8 text. *  CustomPayloadH - The message is a custom format defined by the Lambda function. * SSML? - The message contains text formatted for voice output. *  Composite - The message contains an escaped JSON object containing one or more messages from the groups that messages were assigned to when the intent was created.9 - 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.typeB 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.: - If the  dialogState value is  ElicitSlotJ , returns the name of the slot for which Amazon Lex is eliciting a value.;R - A map of key-value pairs representing the session-specific context information.<! - -- | The response status code.4amazonka-lex-runtimeThe 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 valueSelectionStrategy8 selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUEc , 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 .5amazonka-lex-runtimeRepresents 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).6amazonka-lex-runtime4The current user intent that Amazon Lex is aware of.7amazonka-lex-runtimehIdentifies the current state of the user interaction. Amazon Lex returns one of the following values as  dialogStateZ . The client can optionally use this information to customize the user interface. *  ElicitIntent - Amazon Lex wants to elicit user intent. For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialogState. *  ConfirmIntent - Amazon Lex is expecting a "yes" or "no" response. For example, Amazon Lex wants user confirmation before fulfilling an intent. Instead of a simple "yes" or "no," a user might respond with additional information. For example, "yes, but make it thick crust pizza" or "no, I want to order a drink". Amazon Lex can process such additional information (in these examples, update the crust type slot value, or change intent from OrderPizza to OrderDrink). *  ElicitSlot - Amazon Lex is expecting a slot value for the current intent. For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately. *  Fulfilledl - Conveys that the Lambda function configured for the intent has successfully fulfilled the intent. * ReadyForFulfillment= - Conveys that the client has to fulfill the intent. * FailedF - Conveys that the conversation with the user failed. This can happen for various reasons including that the user did not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or the Lambda function failed to fulfill the intent.8amazonka-lex-runtimeGThe format of the response message. One of the following values: *  PlainText0 - The message contains plain UTF-8 text. *  CustomPayloadH - The message is a custom format defined by the Lambda function. * SSML? - The message contains text formatted for voice output. *  Composite - The message contains an escaped JSON object containing one or more messages from the groups that messages were assigned to when the intent was created.9amazonka-lex-runtimeThe 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.typeB 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.:amazonka-lex-runtimeIf the  dialogState value is  ElicitSlotJ , returns the name of the slot for which Amazon Lex is eliciting a value.;amazonka-lex-runtimeOA map of key-value pairs representing the session-specific context information.<amazonka-lex-runtime- | The response status code.,amazonka-lex-runtime/amazonka-lex-runtime0amazonka-lex-runtime1amazonka-lex-runtime23amazonka-lex-runtime<*+,-./0123456789:;<,+-./0123*456789:;<(c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)None "#27HVPMamazonka-lex-runtimeSee: X smart constructor.Namazonka-lex-runtimeSee: O smart constructor.Oamazonka-lex-runtimeCreates a value of N4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired:P - You pass this value as the Accepth 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. * If the value is text/plain; charset=utf-8L , Amazon Lex returns text in the response. * If the value begins with audio/ , Amazon Lex returns speech in the response. Amazon Lex uses Amazon Polly to generate the speech (using the configuration you specified in the Accept& header). For example, if you specify  audio/mpego as the value, Amazon Lex returns speech in the MPEG format. The following are the accepted values: * audiompeg * audioogg * audiopcm * text5plain; charset=utf-8 * audio/* (defaults to mpeg)Q - 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:Y is reserved for special attributes. Don't create any request attributes with the prefix  x-amz-lex: . For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribsSetting Request Attributes .R - 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 requestAttributes8 headers is limited to 12 KB. For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribsSetting Session Attributes .S - Name of the Amazon Lex bot.T - Alias of the Amazon Lex bot.U - 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 userIDe field. To decide the user ID to use for your application, consider the following factors. * The userID7 field must not contain any personally identifiable information of the user, for example, name, personal identification numbers, or other end user personal information. * If you want a user to start a conversation on one device and continue on another device, use a user-specific identifier. * If you want the same user to be able to have two independent conversations on two different devices, choose a device-specific identifier. * A user can't have two independent conversations with two different versions of the same bot. For example, a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will need to have conversation with two different versions, for example, while testing, include the bot alias in the user ID to separate the two conversations.V - 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: * PCM format, audio data must be in little-endian byte order. * audio'l16; rate=16000; channels=1 * audio5x-l16; sample-rate=16000; channel-count=1 * audioplpcm; sample-rate=8000; sample-size-bits=16; channel-count=1; is-big-endian=false * Opus format * audiox-cbr-opus-with-preamble; preamble-size=0; bit-rate=256000; frame-size-milliseconds=4 * Text format * text/plain; charset=utf-8WM - 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.Pamazonka-lex-runtimeYou pass this value as the Accepth 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. * If the value is text/plain; charset=utf-8L , Amazon Lex returns text in the response. * If the value begins with audio/ , Amazon Lex returns speech in the response. Amazon Lex uses Amazon Polly to generate the speech (using the configuration you specified in the Accept& header). For example, if you specify  audio/mpego as the value, Amazon Lex returns speech in the MPEG format. The following are the accepted values: * audiompeg * audioogg * audiopcm * text5plain; charset=utf-8 * audio/* (defaults to mpeg)Qamazonka-lex-runtimeYou 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:Y is reserved for special attributes. Don't create any request attributes with the prefix  x-amz-lex: . For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-request-attribsSetting Request Attributes .Ramazonka-lex-runtimeYou 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 requestAttributes8 headers is limited to 12 KB. For more information, see  Whttp://docs.aws.amazon.com/lex/latest/dg/context-mgmt.html#context-mgmt-session-attribsSetting Session Attributes .Samazonka-lex-runtimeName of the Amazon Lex bot.Tamazonka-lex-runtimeAlias of the Amazon Lex bot.Uamazonka-lex-runtimeThe 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 userIDe field. To decide the user ID to use for your application, consider the following factors. * The userID7 field must not contain any personally identifiable information of the user, for example, name, personal identification numbers, or other end user personal information. * If you want a user to start a conversation on one device and continue on another device, use a user-specific identifier. * If you want the same user to be able to have two independent conversations on two different devices, choose a device-specific identifier. * A user can't have two independent conversations with two different versions of the same bot. For example, a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will need to have conversation with two different versions, for example, while testing, include the bot alias in the user ID to separate the two conversations.Vamazonka-lex-runtimeYou 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: * PCM format, audio data must be in little-endian byte order. * audio'l16; rate=16000; channels=1 * audio5x-l16; sample-rate=16000; channel-count=1 * audioplpcm; sample-rate=8000; sample-size-bits=16; channel-count=1; is-big-endian=false * Opus format * audiox-cbr-opus-with-preamble; preamble-size=0; bit-rate=256000; frame-size-milliseconds=4 * Text format * text/plain; charset=utf-8Wamazonka-lex-runtimeJUser 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.Xamazonka-lex-runtimeCreates a value of M4 with the minimum fields required to make a request.BUse one of the following lenses to modify other fields as desired: Y - Map of zero or more intent slots (name/value pairs) 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 valueSelectionStrategy8 selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUEc , 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 .Z3 - Current user intent that Amazon Lex is aware of.[k - Identifies the current state of the user interaction. Amazon Lex returns one of the following values as  dialogStateZ . The client can optionally use this information to customize the user interface. *  ElicitIntent - Amazon Lex wants to elicit the user's intent. Consider the following examples: For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialog state. *  ConfirmIntent - Amazon Lex is expecting a "yes" or "no" response. For example, Amazon Lex wants user confirmation before fulfilling an intent. Instead of a simple "yes" or "no" response, a user might respond with additional information. For example, "yes, but make it a thick crust pizza" or "no, I want to order a drink." Amazon Lex can process such additional information (in these examples, update the crust type slot or change the intent from OrderPizza to OrderDrink). *  ElicitSlot - Amazon Lex is expecting the value of a slot for the current intent. For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately. *  FulfilledR - Conveys that the Lambda function has successfully fulfilled the intent. * ReadyForFulfillment> - Conveys that the client has to fulfill the request. * FailedJ - Conveys that the conversation with the user failed. This can happen for various reasons, including that the user does not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or if the Lambda function fails to fulfill the intent.\O - 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.]J - The format of the response message. One of the following values: *  PlainText0 - The message contains plain UTF-8 text. *  CustomPayload8 - The message is a custom format for the client. * SSML? - The message contains text formatted for voice output. *  Composite - The message contains an escaped JSON object containing one or more messages from the groups that messages were assigned to when the intent was created.^ - 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.typeB 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._ - If the  dialogState value is  ElicitSlotJ , returns the name of the slot for which Amazon Lex is eliciting a value.`$ - Content type as specified in the Accept HTTP header in the request.aP - Map of key/value pairs representing the session-specific context information.b! - -- | The response status code.c - 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 clarificationPromptp 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.Yamazonka-lex-runtimeMap of zero or more intent slots (name/value pairs) 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 valueSelectionStrategy8 selected when the slot type was created or updated. If valueSelectionStrategy is set to ORIGINAL_VALUEc , 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 .Zamazonka-lex-runtime0Current user intent that Amazon Lex is aware of.[amazonka-lex-runtimehIdentifies the current state of the user interaction. Amazon Lex returns one of the following values as  dialogStateZ . The client can optionally use this information to customize the user interface. *  ElicitIntent - Amazon Lex wants to elicit the user's intent. Consider the following examples: For example, a user might utter an intent ("I want to order a pizza"). If Amazon Lex cannot infer the user intent from this utterance, it will return this dialog state. *  ConfirmIntent - Amazon Lex is expecting a "yes" or "no" response. For example, Amazon Lex wants user confirmation before fulfilling an intent. Instead of a simple "yes" or "no" response, a user might respond with additional information. For example, "yes, but make it a thick crust pizza" or "no, I want to order a drink." Amazon Lex can process such additional information (in these examples, update the crust type slot or change the intent from OrderPizza to OrderDrink). *  ElicitSlot - Amazon Lex is expecting the value of a slot for the current intent. For example, suppose that in the response Amazon Lex sends this message: "What size pizza would you like?". A user might reply with the slot value (e.g., "medium"). The user might also provide additional information in the response (e.g., "medium thick crust pizza"). Amazon Lex can process such additional information appropriately. *  FulfilledR - Conveys that the Lambda function has successfully fulfilled the intent. * ReadyForFulfillment> - Conveys that the client has to fulfill the request. * FailedJ - Conveys that the conversation with the user failed. This can happen for various reasons, including that the user does not provide an appropriate response to prompts from the service (you can configure how many times Amazon Lex can prompt a user for specific information), or if the Lambda function fails to fulfill the intent.\amazonka-lex-runtimeLThe 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.]amazonka-lex-runtimeGThe format of the response message. One of the following values: *  PlainText0 - The message contains plain UTF-8 text. *  CustomPayload8 - The message is a custom format for the client. * SSML? - The message contains text formatted for voice output. *  Composite - The message contains an escaped JSON object containing one or more messages from the groups that messages were assigned to when the intent was created.^amazonka-lex-runtimeThe 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.typeB 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._amazonka-lex-runtimeIf the  dialogState value is  ElicitSlotJ , returns the name of the slot for which Amazon Lex is eliciting a value.`amazonka-lex-runtime!Content type as specified in the Accept HTTP header in the request.aamazonka-lex-runtimeMMap of key/value pairs representing the session-specific context information.bamazonka-lex-runtime- | The response status code.camazonka-lex-runtimeThe 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 clarificationPromptp 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.Oamazonka-lex-runtimeSamazonka-lex-runtimeTamazonka-lex-runtimeUamazonka-lex-runtimeVamazonka-lex-runtimeWXamazonka-lex-runtimebamazonka-lex-runtimecMNOPQRSTUVWXYZ[\]^_`abcONPQRSTUVWXMYZ[\]^_`abc(c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)NoneHVS~(c) 2013-2018 Brendan HayMozilla Public License, v. 2.0..Brendan Hay <brendan.g.hay+amazonka@gmail.com>auto-generatednon-portable (GHC extensions)NoneUT  !"#$%&'()*+,-./0123456789:;<MNOPQRSTUVWXYZ[\]^_`abc* !"#$%&'()  z      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~1amazonka-lex-runtime-1.6.1-Hd9cm3dncWCDjYObOvteWjNetwork.AWS.LexRuntime.TypesNetwork.AWS.LexRuntime.PostText"Network.AWS.LexRuntime.PostContent Network.AWS.LexRuntime.Types.Sum$Network.AWS.LexRuntime.Types.ProductNetwork.AWS.LexRuntime.WaitersNetwork.AWS.LexRuntimeMessageFormatType Composite CustomPayload PlainTextSsml DialogState ConfirmIntent ElicitIntent ElicitSlotFailed FulfilledReadyForFulfillment ContentType%ApplicationVnd_Amazonaws_Card_Generic ResponseCardGenericAttachmentButtonbuttonbTextbValuegenericAttachment gaButtons gaSubTitle gaImageURLgaAttachmentLinkURLgaTitle responseCardrcGenericAttachments rcVersion rcContentType lexRuntime_NotAcceptableException_DependencyFailedException_UnsupportedMediaTypeException_ConflictException_NotFoundException_RequestTimeoutException_LoopDetectedException_InternalFailureException_BadGatewayException_BadRequestException_LimitExceededExceptionPostTextResponsePostTextpostTextptRequestAttributesptSessionAttributes ptBotName ptBotAliasptUserId ptInputTextpostTextResponse ptrsSlotsptrsResponseCardptrsIntentNameptrsDialogStateptrsMessageFormat ptrsMessageptrsSlotToElicitptrsSessionAttributesptrsResponseStatus$fToQueryPostText$fToPathPostText$fToJSONPostText$fToHeadersPostText$fNFDataPostText$fHashablePostText$fNFDataPostTextResponse$fAWSRequestPostText $fEqPostText$fShowPostText$fDataPostText$fGenericPostText$fEqPostTextResponse$fShowPostTextResponse$fDataPostTextResponse$fGenericPostTextResponsePostContentResponse PostContent postContentpcAcceptpcRequestAttributespcSessionAttributes pcBotName pcBotAliaspcUserId pcContentType pcInputStreampostContentResponse pcrsSlotspcrsIntentNamepcrsDialogStatepcrsInputTranscriptpcrsMessageFormat pcrsMessagepcrsSlotToElicitpcrsContentTypepcrsSessionAttributespcrsResponseStatuspcrsAudioStream$fToQueryPostContent$fToPathPostContent$fToHeadersPostContent$fToBodyPostContent$fAWSRequestPostContent$fShowPostContent$fGenericPostContent$fShowPostContentResponse$fGenericPostContentResponse ResponseCard'_rcContentType _rcVersion_rcGenericAttachmentsGenericAttachment'_gaTitle_gaAttachmentLinkURL _gaImageURL _gaSubTitle _gaButtonsButton'_bValue_bText