See: newPostText smart constructor.

Create a value of PostText with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:activeContexts:PostText', postText_activeContexts - A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by including the context in the request,

If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you specify an empty list, all contexts for the session are cleared.

$sel:requestAttributes:PostText', postText_requestAttributes - 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.

$sel:sessionAttributes:PostText', postText_sessionAttributes - Application-specific information passed between Amazon Lex and a client application.

For more information, see Setting Session Attributes.

$sel:botName:PostText', postText_botName - The name of the Amazon Lex bot.

$sel:botAlias:PostText', postText_botAlias - The alias of the Amazon Lex bot.

$sel:userId:PostText', postText_userId - 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.

• The userID 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.

$sel:inputText:PostText', postText_inputText - The text that the user entered (Amazon Lex interprets this text).

A list of contexts active for the request. A context can be activated when a previous intent is fulfilled, or by including the context in the request,

If you don't specify a list of contexts, Amazon Lex will use the current list of contexts for the session. If you specify an empty list, all contexts for the session are cleared.

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.

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

For more information, see Setting Session Attributes.

The name of the Amazon Lex bot.

The alias of the Amazon Lex bot.

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.

• The userID 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.

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

See: newPostTextResponse smart constructor.

Create a value of PostTextResponse with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:sentimentResponse:PostTextResponse', postTextResponse_sentimentResponse - The sentiment expressed in and utterance.

When the bot is configured to send utterances to Amazon Comprehend for sentiment analysis, this field contains the result of the analysis.

$sel:nluIntentConfidence:PostTextResponse', postTextResponse_nluIntentConfidence - Provides a score that indicates how confident Amazon Lex is that the returned intent is the one that matches the user's intent. The score is between 0.0 and 1.0. For more information, see Confidence Scores.

The score is a relative score, not an absolute score. The score may change based on improvements to Amazon Lex.

$sel:slots:PostTextResponse', postTextResponse_slots - 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.

$sel:responseCard:PostTextResponse', postTextResponse_responseCard - 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).

$sel:intentName:PostTextResponse', postTextResponse_intentName - The current user intent that Amazon Lex is aware of.

$sel:botVersion:PostTextResponse', postTextResponse_botVersion - The version of the bot that responded to the conversation. You can use this information to help determine if one version of a bot is performing better than another version.

$sel:dialogState:PostTextResponse', postTextResponse_dialogState - 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.

• 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.

• Fulfilled - Conveys that the Lambda function configured for the intent has successfully fulfilled the intent.
• ReadyForFulfillment - Conveys that the client has to fulfill the intent.

• Failed - 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.

$sel:activeContexts:PostText', postTextResponse_activeContexts - A list of active contexts for the session. A context can be set when an intent is fulfilled or by calling the PostContent, PostText, or PutSession operation.

You can use a context to control the intents that can follow up an intent, or to modify the operation of your application.

$sel:alternativeIntents:PostTextResponse', postTextResponse_alternativeIntents - One to four alternative intents that may be applicable to the user's intent.

Each alternative includes a score that indicates how confident Amazon Lex is that the intent matches the user's intent. The intents are sorted by the confidence score.

$sel:messageFormat:PostTextResponse', postTextResponse_messageFormat - The format of the response message. One of the following values:

• PlainText - The message contains plain UTF-8 text.
• CustomPayload - 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.

$sel:message:PostTextResponse', postTextResponse_message - 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.

$sel:sessionId:PostTextResponse', postTextResponse_sessionId - A unique identifier for the session.

$sel:slotToElicit:PostTextResponse', postTextResponse_slotToElicit - If the dialogState value is ElicitSlot, returns the name of the slot for which Amazon Lex is eliciting a value.

$sel:sessionAttributes:PostText', postTextResponse_sessionAttributes - A map of key-value pairs representing the session-specific context information.

$sel:httpStatus:PostTextResponse', postTextResponse_httpStatus - The response's http status code.

The sentiment expressed in and utterance.

When the bot is configured to send utterances to Amazon Comprehend for sentiment analysis, this field contains the result of the analysis.

Provides a score that indicates how confident Amazon Lex is that the returned intent is the one that matches the user's intent. The score is between 0.0 and 1.0. For more information, see Confidence Scores.

The score is a relative score, not an absolute score. The score may change based on improvements to Amazon Lex.

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.

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).

The current user intent that Amazon Lex is aware of.

The version of the bot that responded to the conversation. You can use this information to help determine if one version of a bot is performing better than another version.

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.

• 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.

• Fulfilled - Conveys that the Lambda function configured for the intent has successfully fulfilled the intent.
• ReadyForFulfillment - Conveys that the client has to fulfill the intent.

• Failed - 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.

A list of active contexts for the session. A context can be set when an intent is fulfilled or by calling the PostContent, PostText, or PutSession operation.

You can use a context to control the intents that can follow up an intent, or to modify the operation of your application.

One to four alternative intents that may be applicable to the user's intent.

Each alternative includes a score that indicates how confident Amazon Lex is that the intent matches the user's intent. The intents are sorted by the confidence score.

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

• PlainText - The message contains plain UTF-8 text.
• CustomPayload - 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.

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.

A unique identifier for the session.

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

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

The response's http status code.