Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that Amazon Connect Participant Service can respond with.

Structs

• AttachmentItem

  The case-insensitive input to indicate standard MIME type that describes the format of the file that will be uploaded.

• ConnectionCredentials

  Connection credentials.

• Item

  An item - message or event - that has been sent.

• MessageMetadata

  Contains metadata related to a message.

• Receipt

  The receipt for the message delivered to the recipient.

• StartPosition

  A filtering option for where to start. For example, if you sent 100 messages, start with message 50.

• UploadMetadata

  Fields to be used while uploading the attachment.

• View

  A view resource object. Contains metadata and content necessary to render the view.

• ViewContent

  View content containing all content necessary to render a view except for runtime input data.

• Websocket

  The websocket for the participant's connection.

Enums

• ArtifactStatus
  When writing a match expression against ArtifactStatus, 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.
• ChatItemType
  When writing a match expression against ChatItemType, 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.
• ConnectionType
  When writing a match expression against ConnectionType, 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.
• ParticipantRole
  When writing a match expression against ParticipantRole, 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.
• ResourceType
  When writing a match expression against ResourceType, 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.
• ScanDirection
  When writing a match expression against ScanDirection, 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.
• SortKey
  When writing a match expression against SortKey, 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.