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 (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.
PostContent operation supports audio input at 8kHz and 16kHz. You
can use 8kHz audio to achieve higher speech recognition accuracy in telephone audio
In response, Amazon Lex returns the next message to convey to the user. 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 get user confirmation: "Order the pizza?".
After the user replies "Yes" to the confirmation prompt, Amazon Lex might return a conclusion statement: "Thank you, your cheese pizza has been ordered.".
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:
If the message is to elicit slot data, Amazon Lex returns the following context information:
x-amz-lex-dialog-state header set to
x-amz-lex-intent-name header set to the intent name in the current context
x-amz-lex-slot-to-elicit header set to the slot name for which the
is eliciting information
x-amz-lex-slots header set to a map of slots configured for the intent
with their current values
If the message is a confirmation prompt, the
header is set to
Confirmation and the
header is omitted.
If the message is a clarification prompt configured for the intent, indicating that
the user intent is not understood, the
x-amz-dialog-state header is set
ElicitIntent and the
x-amz-slot-to-elicit header is omitted.
In addition, Amazon Lex also returns your application-specific
For more information, see Managing
For .NET Core and PCL this operation is only available in asynchronous form. Please refer to PostContentAsync.
public abstract PostContentResponse PostContent( PostContentRequest request )
Container for the necessary parameters to execute the PostContent service method.
|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.|
|NotAcceptableException||The accept header in the request does not have a valid value.|
|NotFoundException||The resource (such as the Amazon Lex bot or an alias) that is referred to is not found.|
|RequestTimeoutException||The input speech is too long.|
|UnsupportedMediaTypeException||The Content-Type header (PostContent API) has an invalid value.|
Supported in: 4.5, 4.0, 3.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms