Check attachment staleness

Base URL: https://{kibana_url}

GET /api/agent_builder/conversations/{conversation_id}/attachments/stale
GET /s/{space_id}/api/agent_builder/conversations/{conversation_id}/attachments/stale

Refer to Spaces for more information.

Checks staleness for the latest version of all conversation attachments against their origin snapshot.

Authentication

Api key

Authorization: <value>

These APIs use key-based authentication. You must create an API key and use the encoded value in the request header. For example: Authorization: ApiKey base64AccessApiKey

Basic

Authorization: Basic <credentials>

Mixed conversation: attachments without a stale source return only id and is_stale. When a staleness check fails for one attachment, is_stale is false and an error explains why. When an origin-backed attachment is out of date, the response includes type, origin, and resolved data (here a simple text body) for resync.

{
  "attachments": [
    {
      "id": "att-text-meeting-notes",
      "is_stale": false
    },
    {
      "id": "att-lens-active-users",
      "is_stale": false
    },
    {
      "error": "Origin could not be resolved",
      "id": "att-query-attachment",
      "is_stale": false
    },
    {
      "data": "This is the content of my text attachment",
      "hidden": false,
      "id": "att-text-runbook",
      "is_stale": true,
      "origin": "document:hr-onboarding-v2",
      "type": "text"
    }
  ]
}

Check attachment staleness

Required authorization

Authentication

Path parameters

Response