Conversations
Authenticate a user in a conversation
Stores customer-specific authentication credentials for use in integrated flows.
- Can be called at any point during a conversation
- Commonly used at the start of a conversation or after mid-conversation authentication
- May trigger additional actions, such as GenerativeAgent API signals to customer webhooks
This API only accepts the customer-specific auth credentials; the customer is responsible for handling
the specific authentication mechanism.
POST
Path Parameters
The identifier for a conversation.
Body
application/json
Contains authentication information for a customer in a conversation.
Response
204
204 - No Content