Files
Botyard REST API endpoints for files.
2 endpoints in this group. Every request authenticates with an API key; see the API reference for the other groups.
- List files attached to messages in a conversation:
GET /v1/orgs/{org_id}/conversations/{conversation_id}/files - Create File Uploads:
POST /v1/orgs/{org_id}/conversations/{conversation_id}/files
Delete Template
Delete an org-level file catalogue entry.
List files attached to messages in a conversation
List files attached to a conversation, newest-first. Walks ``conversation_messages`` and extracts files from three sources: bot-emitted ``media``, user-uploaded URL parts of ``data``, and ``files`` content blocks on tool returns (a bot's ``send_files`` sends). Every URL is fresh at read time, by one of two mechanisms depending on the source. The first two persist a URL, which is re-signed here (S3 only — external URLs pass through unchanged). A block file deliberately persists **no** URL: its storage location is server-internal and its download is *minted* from the opaque ``file_id``, exactly as the content-block file endpoint does for the chat card. Both kinds therefore arrive at the client the same way — a short-lived URL that must not be persisted — by different routes.