Files
Get file metadata
Authorization
api_key files:readAuthorizationBearer <token>
An atk_-prefixed API key, created under Settings → API keys.
In: header
Scope: files:read
Path Parameters
file_id*string
File id
Format
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/files/497f6eca-6276-4993-bfeb-53cbbbba6f08"{ "artifact_key": "string", "changelog": "string", "content_type": "string", "created_at": "2019-08-24T14:15:22Z", "filename": "string", "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "kind": "string", "path": "string", "pinned": true, "session_id": "1ffd059c-17ea-40a8-8aef-70fd0307db82", "size_bytes": 0, "title": "string", "version": 0}Upload a file POST
Multipart form with fields `session_id`, `filename`, `content_type`, and `file`. The bytes land in the account's Computer workspace under `uploads/` — the agent reads them back with its `computer_file_*` tools, and you download them again with `GET /v1/files/{file_id}/content`. The file is registered against the session it was uploaded to, so it is only reachable (and only readable by an agent working that chat) through a session the key's account owns.
Download a file's bytes GET
The raw bytes, served with the file's own content type.