AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Sends user input 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:
For a user input "I would like a pizza", Amazon Lex might return a response with a message eliciting slot data (for example, PizzaSize): "What size pizza would you like?"
After the user provides all of the pizza order information, Amazon Lex might return a response with a message to obtain user confirmation "Proceed with the pizza order?".
After the user replies to a confirmation prompt with a "yes", Amazon Lex might return a conclusion statement: "Thank you, your cheese pizza has been ordered.".
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:
If the message is to elicit slot data, Amazon Lex returns the following context information:
dialogState set to ElicitSlot
intentName set to the intent name in the current context
slotToElicit set to the slot name for which the message is eliciting
information
slots set to a map of slots, configured for the intent, with currently known
values
If the message is a confirmation prompt, the dialogState is set to ConfirmIntent
and SlotToElicit is set to null.
If the message is a clarification prompt (configured for the intent) that indicates
that user intent is not understood, the dialogState is set to ElicitIntent
and slotToElicit is set to null.
In addition, Amazon Lex also returns your application-specific sessionAttributes.
For more information, see Managing
Conversation Context.
For .NET Core this operation is only available in asynchronous form. Please refer to PostTextAsync.
Namespace: Amazon.Lex
Assembly: AWSSDK.Lex.dll
Version: 3.x.y.z
public abstract PostTextResponse PostText( PostTextRequest request )
Container for the necessary parameters to execute the PostText service method.
| Exception | Condition |
|---|---|
| BadGatewayException | Either the Amazon Lex bot is still building, or one of the dependent services (Amazon Polly, AWS Lambda) failed with an internal service error. |
| BadRequestException | Request validation failed, there is no usable message in the context, or the bot build failed, is still in progress, or contains unbuilt changes. |
| ConflictException | Two clients are using the same AWS account, Amazon Lex bot, and user ID. |
| DependencyFailedException | One of the dependencies, such as AWS Lambda or Amazon Polly, threw an exception. For example, If 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 Delegate dialog action without removing any slot values. |
| InternalFailureException | Internal service error. Retry the call. |
| LimitExceededException | Exceeded a limit. |
| LoopDetectedException | This exception is not used. |
| NotFoundException | The resource (such as the Amazon Lex bot or an alias) that is referred to is not found. |
.NET Framework:
Supported in: 4.5, 4.0, 3.5