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
/
conversation
/
v1
/
conversations
/
{conversationId}
/
authenticate
Authorizations
asapp-api-id
string
headerrequiredasapp-api-secret
string
headerrequiredPath Parameters
conversationId
string
requiredThe identifier for a conversation.
Body
application/json
Contains authentication information for a customer in a conversation.
streamId
string
The unique identifier for the connection where responses should be sent.
customerExternalId
string
requiredThe unique identifier for the customer in your external system.
auth
object
requiredAn authentication payload that could contain different types of credentials, such as a token, used to authenticate an end user. All of the fields are optional, but at least one will be required
Was this page helpful?