send_chat_integration_event
¶
send_chat_integration_event(
source_id: SourceId,
destination_id: DestinationId,
event: ChatEvent,
*,
config_overrides: Optional[ConnectClientConfig] = None,
subtype: Optional[Subtype] = None,
new_session_details: Optional[NewSessionDetails] = None,
) -> SendChatIntegrationEventResponse
Processes chat integration events from Amazon Web Services or external integrations to Connect Customer. A chat integration event includes:
-
SourceId, DestinationId, and Subtype: a set of identifiers, uniquely representing a chat
-
ChatEvent: details of the chat action to perform such as sending a message, event, or disconnecting from a chat
When a chat integration event is sent with chat identifiers that do not map to an active chat contact, a new chat contact is also created before handling chat action.
Access to this API is currently restricted to Amazon Web Services End User Messaging for supporting SMS integration.
Parameters:
-
source_id(SourceId) –External identifier of chat customer participant, used in part to uniquely identify a chat. For SMS, this is the E164 phone number of the chat customer participant.
-
destination_id(DestinationId) –Chat system identifier, used in part to uniquely identify chat. This is associated with the Connect Customer instance and flow to be used to start chats. For Server Migration Service, this is the phone number destination of inbound Server Migration Service messages represented by an Amazon Web Services End User Messaging phone number ARN.
-
subtype(Optional[Subtype], default:None) –Classification of a channel. This is used in part to uniquely identify chat.
Valid value:
["connect:sms", connect:"WhatsApp"] -
event(ChatEvent) –Chat integration event payload
-
new_session_details(Optional[NewSessionDetails], default:None) –Contact properties to apply when starting a new chat. If the integration event is handled with an existing chat, this is ignored.
Raises:
-
AccessDeniedException–You do not have sufficient permissions to perform this action.
-
InternalServiceException–Request processing failed because of an error or failure with the service.
-
InvalidRequestException–The request is not valid.
-
ResourceNotFoundException–The specified resource was not found.
-
ThrottlingException–The throttling limit has been exceeded.
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_connect/_services/connect.py
22573 22574 22575 22576 22577 22578 22579 22580 22581 22582 22583 22584 22585 22586 22587 22588 22589 22590 22591 22592 22593 22594 22595 22596 22597 22598 22599 22600 22601 22602 22603 22604 22605 22606 22607 22608 22609 22610 22611 22612 22613 22614 22615 22616 22617 22618 22619 22620 22621 22622 22623 22624 22625 22626 22627 22628 22629 22630 22631 22632 22633 22634 22635 22636 | |