Check attachment staleness Technical Preview; added in 9.4.0

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

Spaces method and path for this operation:

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.

[Required authorization] Route required privileges: agentBuilder:read.

Path parameters

  • conversation_id string Required

    The unique identifier of the conversation.

Responses

  • 200 application/json

    Indicates a successful response

GET /api/agent_builder/conversations/{conversation_id}/attachments/stale
curl \
 --request GET 'https://localhost:5601/api/agent_builder/conversations/{conversation_id}/attachments/stale' \
 --header "Authorization: $API_KEY"
Response examples (200)
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
    },
    {
      "id": "att-query-attachment",
      "error": "Origin could not be resolved",
      "is_stale": false
    },
    {
      "id": "att-text-runbook",
      "data": "This is the content of my text attachment",
      "type": "text",
      "hidden": false,
      "origin": "document:hr-onboarding-v2",
      "is_stale": true
    }
  ]
}