Expand description

Data structures used by operation inputs/outputs.

Modules

  • Builders
  • Error types that Amazon Lex Runtime V2 can respond with.

Structs

  • Contains information about the contexts that a user is using in a session. You can configure Amazon Lex V2 to set a context when an intent is fulfilled, or you can set a context using the , , or operations.

  • The time that a context is active. You can specify the time to live in seconds or in conversation turns.

  • A button that appears on a response card show to the user.

  • Provides a score that indicates the confidence that Amazon Lex V2 has that an intent is the one that satisfies the user's intent.

  • The next action that Amazon Lex V2 should take.

  • The specific constituent sub slot of the composite slot to elicit in dialog action.

  • A card that is shown to the user by a messaging platform. You define the contents of the card, the card is displayed by the platform.

  • The current intent that Amazon Lex V2 is attempting to fulfill.

  • An intent that Amazon Lex V2 determined might satisfy the user's utterance. The intents are ordered by the confidence score.

  • Container for text that is returned to the customer..

  • The bot member that processes the request.

  • Provides an array of phrases that should be given preference when resolving values for a slot.

  • Provides the phrase that Amazon Lex V2 should look for in the user's input to the bot.

  • You can provide Amazon Lex V2 with hints to the phrases that a customer is likely to use for a slot. When a slot with hints is resolved, the phrases in the runtime hints are preferred in the resolution. You can provide hints for a maximum of 100 intents. You can provide a maximum of 100 slots.

  • Provides information about the sentiment expressed in a user's response in a conversation. Sentiments are determined using Amazon Comprehend. Sentiments are only returned if they are enabled for the bot.

  • The individual sentiment responses for the utterance.

  • The state of the user's session with Amazon Lex V2.

  • A value that Amazon Lex V2 uses to fulfill an intent.

  • The value of a slot.

Enums

  • When writing a match expression against ConfirmationState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against DialogActionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against IntentState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against MessageContentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against SentimentType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against Shape, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against StyleType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.