Request Schema
Event type, available types are:
Value | Description |
---|---|
answer.created | Emitted when a generated answer is sent. |
answer.processing | Emitted when the generation of an answer starts. |
conversation.dropped | Emitted when the conversation exceeds the maximum processing time and no answer could be generated. |
The data object varies for each event type. You will find the details of each data structure below.
Event Data Structures
answer.created
Emitted upon generation of an answer.
Contains a ContentCreationAnswer object.
Example for a TEXT
answer
Example for a ACTION_POKE
answer
TEXT
answer with a conversation stop reason of UNDERAGE_USER
, resulting in a lifetime stop.
answer.processing
Emitted when a conversation enters processing.
It can be used to display a “Persona is typing…” message on your user’s chat interface.
References a project id.
References a user profile id.
References a persona profile id.
Requested reply mode, can be
AI
or HUMAN
.An key/value object.
Example:
{ "key": "value" }
Example
conversation.dropped
Emitted when a conversation exceeds the maximum processing time specified at enqueue.
On receipt of this event, you may requeue the conversation or take no action.
References a project id.
References a user profile id.
References a persona profile id.
Requested reply mode, can be
AI
or HUMAN
.An key/value object.
Example:
{ "key": "value" }