Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Account
The Amazon Chime account details. An AWS account can have multiple Amazon Chime accounts.
- Account
Settings Settings related to the Amazon Chime account. This includes settings that start or stop remote control of shared screens, or start or stop the dial-out option in the Amazon Chime web application. For more information about these settings, see Use the Policies Page in the Amazon Chime Administration Guide.
- Alexa
ForBusiness Metadata The Alexa for Business metadata associated with an Amazon Chime user, used to integrate Alexa for Business with a device.
- Bot
A resource that allows Enterprise account administrators to configure an interface to receive events from Amazon Chime.
- Business
Calling Settings The Amazon Chime Business Calling settings for the administrator's AWS account. Includes any Amazon S3 buckets designated for storing call detail records.
- Conversation
Retention Settings The retention settings that determine how long to retain conversation messages for an Amazon Chime Enterprise account.
- Events
Configuration The configuration that allows a bot to receive outgoing events. Can be either an HTTPS endpoint or a Lambda function ARN.
- Invite
Invitation object returned after emailing users to invite them to join the Amazon Chime
Team
account.- Member
The member details, such as email address, name, member ID, and member type.
- Member
Error The list of errors returned when a member action results in an error.
- Membership
Item Membership details, such as member ID and member role.
- Ordered
Phone Number A phone number for which an order has been placed.
- Phone
Number A phone number used for Amazon Chime Business Calling or an Amazon Chime Voice Connector.
- Phone
Number Association The phone number associations, such as Amazon Chime account ID, Amazon Chime user ID, Amazon Chime Voice Connector ID, or Amazon Chime Voice Connector group ID.
- Phone
Number Capabilities The phone number capabilities for Amazon Chime Business Calling phone numbers, such as enabled inbound and outbound calling and text messaging.
- Phone
Number Country The phone number country.
- Phone
Number Error If the phone number action fails for one or more of the phone numbers in the request, a list of the phone numbers is returned, along with error codes and error messages.
- Phone
Number Order The details of a phone number order created for Amazon Chime.
- Retention
Settings The retention settings for an Amazon Chime Enterprise account that determine how long to retain items such as chat-room messages and chat-conversation messages.
- Room
The Amazon Chime chat room details.
- Room
Membership The room membership details.
- Room
Retention Settings The retention settings that determine how long to retain chat-room messages for an Amazon Chime Enterprise account.
- Signin
Delegate Group An Active Directory (AD) group whose members are granted permission to act as delegates.
- Telephony
Settings Settings that allow management of telephony permissions for an Amazon Chime user, such as inbound and outbound calling and text messaging.
- Update
Phone Number Request Item The phone number ID, product type, or calling name fields to update, used with the
BatchUpdatePhoneNumber
andUpdatePhoneNumber
actions.- Update
User Request Item The user ID and user fields to update, used with the
BatchUpdateUser
action.- User
The user on the Amazon Chime account.
- User
Error The list of errors returned when errors are encountered during the
BatchSuspendUser
,BatchUnsuspendUser
, orBatchUpdateUser
actions. This includes user IDs, error codes, and error messages.- User
Settings Settings associated with an Amazon Chime user, including inbound and outbound calling and text messaging.
- Voice
Connector Settings The Amazon Chime Voice Connector settings. Includes any Amazon S3 buckets designated for storing call detail records.
Enums§
- Account
Status - When writing a match expression against
AccountStatus
, 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. - Account
Type - When writing a match expression against
AccountType
, 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. - BotType
- When writing a match expression against
BotType
, 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. - Calling
Name Status - When writing a match expression against
CallingNameStatus
, 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. - Email
Status - When writing a match expression against
EmailStatus
, 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. - Error
Code - When writing a match expression against
ErrorCode
, 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. - Invite
Status - When writing a match expression against
InviteStatus
, 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. - License
- When writing a match expression against
License
, 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. - Member
Type - When writing a match expression against
MemberType
, 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. - Ordered
Phone Number Status - When writing a match expression against
OrderedPhoneNumberStatus
, 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. - Phone
Number Association Name - When writing a match expression against
PhoneNumberAssociationName
, 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. - Phone
Number Order Status - When writing a match expression against
PhoneNumberOrderStatus
, 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. - Phone
Number Product Type - When writing a match expression against
PhoneNumberProductType
, 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. - Phone
Number Status - When writing a match expression against
PhoneNumberStatus
, 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. - Phone
Number Type - When writing a match expression against
PhoneNumberType
, 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. - Registration
Status - When writing a match expression against
RegistrationStatus
, 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. - Room
Membership Role - When writing a match expression against
RoomMembershipRole
, 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. - User
Type - When writing a match expression against
UserType
, 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.