Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

ChimeSDKMessaging

import { ChimeSDKMessaging } from "https://aws-api.deno.dev/v0.3/services/chimesdkmessaging.ts?docs=full";
class ChimeSDKMessaging {
constructor(apiFactory: client.ApiFactory);
async associateChannelFlow(params: AssociateChannelFlowRequest, opts?: client.RequestOptions): Promise<void>;
async batchCreateChannelMembership(params: BatchCreateChannelMembershipRequest, opts?: client.RequestOptions): Promise<BatchCreateChannelMembershipResponse>;
async channelFlowCallback(params: ChannelFlowCallbackRequest, opts?: client.RequestOptions): Promise<ChannelFlowCallbackResponse>;
async createChannel(params: CreateChannelRequest, opts?: client.RequestOptions): Promise<CreateChannelResponse>;
async createChannelBan(params: CreateChannelBanRequest, opts?: client.RequestOptions): Promise<CreateChannelBanResponse>;
async createChannelFlow(params: CreateChannelFlowRequest, opts?: client.RequestOptions): Promise<CreateChannelFlowResponse>;
async createChannelMembership(params: CreateChannelMembershipRequest, opts?: client.RequestOptions): Promise<CreateChannelMembershipResponse>;
async createChannelModerator(params: CreateChannelModeratorRequest, opts?: client.RequestOptions): Promise<CreateChannelModeratorResponse>;
async deleteChannel(params: DeleteChannelRequest, opts?: client.RequestOptions): Promise<void>;
async deleteChannelBan(params: DeleteChannelBanRequest, opts?: client.RequestOptions): Promise<void>;
async deleteChannelFlow(params: DeleteChannelFlowRequest, opts?: client.RequestOptions): Promise<void>;
async deleteChannelMembership(params: DeleteChannelMembershipRequest, opts?: client.RequestOptions): Promise<void>;
async deleteChannelMessage(params: DeleteChannelMessageRequest, opts?: client.RequestOptions): Promise<void>;
async deleteChannelModerator(params: DeleteChannelModeratorRequest, opts?: client.RequestOptions): Promise<void>;
async describeChannel(params: DescribeChannelRequest, opts?: client.RequestOptions): Promise<DescribeChannelResponse>;
async describeChannelBan(params: DescribeChannelBanRequest, opts?: client.RequestOptions): Promise<DescribeChannelBanResponse>;
async describeChannelFlow(params: DescribeChannelFlowRequest, opts?: client.RequestOptions): Promise<DescribeChannelFlowResponse>;
async describeChannelMembership(params: DescribeChannelMembershipRequest, opts?: client.RequestOptions): Promise<DescribeChannelMembershipResponse>;
async describeChannelModerator(params: DescribeChannelModeratorRequest, opts?: client.RequestOptions): Promise<DescribeChannelModeratorResponse>;
async disassociateChannelFlow(params: DisassociateChannelFlowRequest, opts?: client.RequestOptions): Promise<void>;
async getChannelMembershipPreferences(params: GetChannelMembershipPreferencesRequest, opts?: client.RequestOptions): Promise<GetChannelMembershipPreferencesResponse>;
async getChannelMessage(params: GetChannelMessageRequest, opts?: client.RequestOptions): Promise<GetChannelMessageResponse>;
async getChannelMessageStatus(params: GetChannelMessageStatusRequest, opts?: client.RequestOptions): Promise<GetChannelMessageStatusResponse>;
async getMessagingSessionEndpoint(opts?: client.RequestOptions): Promise<GetMessagingSessionEndpointResponse>;
async listChannelBans(params: ListChannelBansRequest, opts?: client.RequestOptions): Promise<ListChannelBansResponse>;
async listChannelFlows(params: ListChannelFlowsRequest, opts?: client.RequestOptions): Promise<ListChannelFlowsResponse>;
async listChannelMemberships(params: ListChannelMembershipsRequest, opts?: client.RequestOptions): Promise<ListChannelMembershipsResponse>;
async listChannelMessages(params: ListChannelMessagesRequest, opts?: client.RequestOptions): Promise<ListChannelMessagesResponse>;
async listChannelModerators(params: ListChannelModeratorsRequest, opts?: client.RequestOptions): Promise<ListChannelModeratorsResponse>;
async listChannels(params: ListChannelsRequest, opts?: client.RequestOptions): Promise<ListChannelsResponse>;
async listChannelsAssociatedWithChannelFlow(params: ListChannelsAssociatedWithChannelFlowRequest, opts?: client.RequestOptions): Promise<ListChannelsAssociatedWithChannelFlowResponse>;
async listChannelsModeratedByAppInstanceUser(params: ListChannelsModeratedByAppInstanceUserRequest, opts?: client.RequestOptions): Promise<ListChannelsModeratedByAppInstanceUserResponse>;
async listTagsForResource(params: ListTagsForResourceRequest, opts?: client.RequestOptions): Promise<ListTagsForResourceResponse>;
async putChannelMembershipPreferences(params: PutChannelMembershipPreferencesRequest, opts?: client.RequestOptions): Promise<PutChannelMembershipPreferencesResponse>;
async redactChannelMessage(params: RedactChannelMessageRequest, opts?: client.RequestOptions): Promise<RedactChannelMessageResponse>;
async sendChannelMessage(params: SendChannelMessageRequest, opts?: client.RequestOptions): Promise<SendChannelMessageResponse>;
async tagResource(params: TagResourceRequest, opts?: client.RequestOptions): Promise<void>;
async untagResource(params: UntagResourceRequest, opts?: client.RequestOptions): Promise<void>;
async updateChannel(params: UpdateChannelRequest, opts?: client.RequestOptions): Promise<UpdateChannelResponse>;
async updateChannelFlow(params: UpdateChannelFlowRequest, opts?: client.RequestOptions): Promise<UpdateChannelFlowResponse>;
async updateChannelMessage(params: UpdateChannelMessageRequest, opts?: client.RequestOptions): Promise<UpdateChannelMessageResponse>;
async updateChannelReadMarker(params: UpdateChannelReadMarkerRequest, opts?: client.RequestOptions): Promise<UpdateChannelReadMarkerResponse>;
 
static ApiMetadata: client.ApiMetadata;
}

§Constructors

§
new ChimeSDKMessaging(apiFactory: client.ApiFactory)
[src]

§Methods

§
associateChannelFlow(params: AssociateChannelFlowRequest, opts?: client.RequestOptions): Promise<void>
[src]

Associates a channel flow with a channel. Once associated, all messages to that channel go through channel flow processors. To stop processing, use the DisassociateChannelFlow API.

Note: Only administrators or channel moderators can associate a channel flow. The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Adds a specified number of users to a channel.

§

Calls back Chime SDK Messaging with a processing response message. This should be invoked from the processor Lambda. This is a developer API.

You can return one of the following processing responses:

  • Update message content or metadata
  • Deny a message
  • Make no changes to the message
§

Creates a channel to which you can add users and send messages.

Restriction: You can't change a channel's privacy.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Permanently bans a member from a channel. Moderators can't add banned members to a channel. To undo a ban, you first have to DeleteChannelBan, and then CreateChannelMembership. Bans are cleaned up when you delete users or channels.

If you ban a user who is already part of a channel, that user is automatically kicked from the channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Creates a channel flow, a container for processors. Processors are AWS Lambda functions that perform actions on chat messages, such as stripping out profanity. You can associate channel flows with channels, and the processors in the channel flow then take action on all messages sent to that channel. This is a developer API.

Channel flows process the following items:

  1. New and updated messages
  2. Persistent and non-persistent messages
  3. The Standard message type

Note: Channel flows don't process Control or System messages. For more information about the message types provided by Chime SDK Messaging, refer to Message types in the Amazon Chime developer guide.

§

Adds a user to a channel. The InvitedBy field in ChannelMembership is derived from the request header. A channel member can:

  • List messages
  • Send messages
  • Receive messages
  • Edit their own messages
  • Leave the channel

Privacy settings impact this action as follows:

  • Public Channels: You do not need to be a member to list messages, but you must be a member to send messages.
  • Private Channels: You must be a member to list or send messages.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Creates a new ChannelModerator. A channel moderator can:

  • Add and remove other members of the channel.
  • Add and remove other moderators of the channel.
  • Add and remove user bans for the channel.
  • Redact messages in the channel.
  • List messages in the channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§
deleteChannel(params: DeleteChannelRequest, opts?: client.RequestOptions): Promise<void>
[src]

Immediately makes a channel and its memberships inaccessible and marks them for deletion. This is an irreversible process.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§
deleteChannelBan(params: DeleteChannelBanRequest, opts?: client.RequestOptions): Promise<void>
[src]

Removes a user from a channel's ban list.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§
deleteChannelFlow(params: DeleteChannelFlowRequest, opts?: client.RequestOptions): Promise<void>
[src]

Deletes a channel flow, an irreversible process. This is a developer API.

Note: This API works only when the channel flow is not associated with any channel. To get a list of all channels that a channel flow is associated with, use the ListChannelsAssociatedWithChannelFlow API. Use the DisassociateChannelFlow API to disassociate a channel flow from all channels.

§
deleteChannelMembership(params: DeleteChannelMembershipRequest, opts?: client.RequestOptions): Promise<void>
[src]

Removes a member from a channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§
deleteChannelMessage(params: DeleteChannelMessageRequest, opts?: client.RequestOptions): Promise<void>
[src]

Deletes a channel message. Only admins can perform this action. Deletion makes messages inaccessible immediately. A background process deletes any revisions created by UpdateChannelMessage.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§
deleteChannelModerator(params: DeleteChannelModeratorRequest, opts?: client.RequestOptions): Promise<void>
[src]

Deletes a channel moderator.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns the full details of a channel in an Amazon Chime AppInstance.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns the full details of a channel ban.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns the full details of a channel flow in an Amazon Chime AppInstance. This is a developer API.

§

Returns the full details of a user's channel membership.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns the details of a channel based on the membership of the specified AppInstanceUser.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns the full details of a channel moderated by the specified AppInstanceUser.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns the full details of a single ChannelModerator.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§
disassociateChannelFlow(params: DisassociateChannelFlowRequest, opts?: client.RequestOptions): Promise<void>
[src]

Disassociates a channel flow from all its channels. Once disassociated, all messages to that channel stop going through the channel flow processor.

Note: Only administrators or channel moderators can disassociate a channel flow. The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Gets the membership preferences of an AppInstanceUser for the specified channel. The AppInstanceUser must be a member of the channel. Only the AppInstanceUser who owns the membership can retrieve preferences. Users in the AppInstanceAdmin and channel moderator roles can't retrieve preferences for other users. Banned users can't retrieve membership preferences for the channel from which they are banned.

§

Gets the full details of a channel message.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Gets message status for a specified messageId. Use this API to determine the intermediate status of messages going through channel flow processing. The API provides an alternative to retrieving message status if the event was not received because a client wasn't connected to a websocket.

Messages can have any one of these statuses.

SENT: Message processed successfully

PENDING: Ongoing processing

FAILED: Processing failed

DENIED: Messasge denied by the processor

Note: - This API does not return statuses for denied messages, because we don't store them once the processor denies them. - Only the message sender can invoke this API. - The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header

§
getMessagingSessionEndpoint(opts?: client.RequestOptions): Promise<GetMessagingSessionEndpointResponse>
[src]

The details of the endpoint for the messaging session.

§

Lists all the users banned from a particular channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Returns a paginated lists of all the channel flows created under a single Chime. This is a developer API.

§

Lists all channel memberships in a channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

If you want to list the channels to which a specific app instance user belongs, see the ListChannelMembershipsForAppInstanceUser API.

§

Lists all channels that a particular AppInstanceUser is a part of. Only an AppInstanceAdmin can call the API with a user ARN that is not their own.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

List all the messages in a channel. Returns a paginated list of ChannelMessages. By default, sorted by creation timestamp in descending order.

Note: Redacted messages appear in the results as empty, since they are only redacted, not deleted. Deleted messages do not appear in the results. This action always returns the latest version of an edited message. Also, the x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Lists all the moderators for a channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Lists all Channels created under a single Chime App as a paginated list. You can specify filters to narrow results.

Functionality & restrictions

  • Use privacy = PUBLIC to retrieve all public channels in the account.
  • Only an AppInstanceAdmin can set privacy = PRIVATE to list the private channels in an account.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Lists all channels associated with a specified channel flow. You can associate a channel flow with multiple channels, but you can only associate a channel with one channel flow. This is a developer API.

§

A list of the channels moderated by an AppInstanceUser.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Lists the tags applied to an Amazon Chime SDK messaging resource.

§

Sets the membership preferences of an AppInstanceUser for the specified channel. The AppInstanceUser must be a member of the channel. Only the AppInstanceUser who owns the membership can set preferences. Users in the AppInstanceAdmin and channel moderator roles can't set preferences for other users. Banned users can't set membership preferences for the channel from which they are banned.

§

Redacts message content, but not metadata. The message exists in the back end, but the action returns null content, and the state shows as redacted.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Sends a message to a particular channel that the member is a part of.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header. Also, STANDARD messages can contain 4KB of data and the 1KB of metadata. CONTROL messages can contain 30 bytes of data and no metadata.

§
tagResource(params: TagResourceRequest, opts?: client.RequestOptions): Promise<void>
[src]

Applies the specified tags to the specified Amazon Chime SDK messaging resource.

§
untagResource(params: UntagResourceRequest, opts?: client.RequestOptions): Promise<void>
[src]

Removes the specified tags from the specified Amazon Chime SDK messaging resource.

§

Update a channel's attributes.

Restriction: You can't change a channel's privacy.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

Updates channel flow attributes. This is a developer API.

§

Updates the content of a message.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§

The details of the time when a user last read messages in a channel.

Note: The x-amz-chime-bearer request header is mandatory. Use the AppInstanceUserArn of the user that makes the API call as the value in the header.

§Static Properties