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, .
A context is a variable that contains information about the current state of the conversation between a user and Amazon Lex. Context can be set automatically by Amazon Lex when an intent is fulfilled, or it can be set at runtime using the
The length of time or number of turns that a context remains active.
Represents an option to be shown on the client platform (Facebook, Slack, etc.)
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.
Represents an option rendered to the user when a prompt is shown. It could be an image, a button, a link, or text.
Provides a score that indicates the confidence that Amazon Lex has that an intent is the one that satisfies the user's intent.
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.
A client for the Amazon Lex Runtime Service API.
An intent that Amazon Lex suggests satisfies the user's intent. Includes the name of the intent, the confidence that Amazon Lex has that the user's intent is satisfied, and the slots defined for the intent.
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 (
fulfillmentActivity on an intent).
The sentiment expressed in an utterance.
When the bot is configured to send utterances to Amazon Comprehend for sentiment analysis, this field structure contains the result of the analysis.
Errors returned by DeleteSession
Errors returned by GetSession
Errors returned by PostContent
Errors returned by PostText
Errors returned by PutSession
Trait representing the capabilities of the Amazon Lex Runtime Service API. Amazon Lex Runtime Service clients implement this trait.