Add Assistant Attachment To Knowledge

Store an attached file's text in the knowledge base (`POST /kb/documents/text`, as the user: its rules and free-tier budgets apply) and answer what that route answers. 422 when the file has no text (RO-323).

API key access

Not available to API keys or connected apps: only a signed-in person can call this route.

POST/api/v1/assistant/attachments/{attachment_id}/knowledge

Authorization

AuthorizationBearer <token>

Access token from /api/v1/auth/login, or an API key (ro_pat_..., RO-176) from /api/v1/workspaces/current/api-keys: the key implies its workspace and needs the route's scope. MCP connectors (/api/v1/mcp only) may use an OAuth access token (ro_oat_..., RO-284).

In: header

Path Parameters

attachment_idstring

Formatuuid

Header Parameters

X-Workspace-Id?string | null

Id of the workspace to act on (must be a member).

Request Body

title?string | null

Default: the file's name.

Length1 <= length <= 500

Response Body

curl -X POST "http://localhost:8000/api/v1/assistant/attachments/497f6eca-6276-4993-bfeb-53cbbbba6f08/knowledge" \
  -H "X-Workspace-Id: string" \
  -H "Content-Type: application/json" \
  -d '{}'

curl -X POST "http://localhost:8000/api/v1/assistant/attachments/497f6eca-6276-4993-bfeb-53cbbbba6f08/knowledge" \  -H "X-Workspace-Id: string" \  -H "Content-Type: application/json" \  -d '{}'

Empty

{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string",
      "input": null,
      "ctx": {}
    }
  ]
}