Type to search.

Add events to a conversation

Base URL
https://{kibana_url}
Auth The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability Planned We plan to add this functionality in a future Elastic Stack update. Subject to changes. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

Append custom events to a conversation's timeline. The caller must be the owner, a member, or the conversation must be public. Server assigns id, created_at, and actor for each event; the body provides type and data. Only registered custom event types are accepted — built-in lifecycle types are rejected. To learn more about agent conversations, refer to the agent chat documentation.

Required privileges

Privileges agentBuilder:read

Path parameters

space_id string optional

An identifier for the space. If space_id is not provided in the URL, the default space is used. Refer to Spaces for more information.

conversation_id string · max length: 256 required

The unique identifier of the conversation.

Header parameters

kbn-xsrf string required

A required header to protect against CSRF attacks

Request body

events object[] · min items: 1 · max items: 10 required

Events to append. Between 1 and 10.

data object required

The event payload. Its shape is defined by the event type.

type string · min length: 1 · max length: 256 required

The registered custom event type.

Response

200

Indicates a successful response

application/json