List a chat's artifacts
Everything the agent produced in this chat, every revision included. Files you sent it are not artifacts and do not appear here.
Everything the agent produced in this chat, every revision included. Files you sent it are not artifacts and do not appear here.
Authorization
api_key sessions:read, artifacts:readAn atk_-prefixed API key, created under Settings → API keys.
In: header
Scope: sessions:read, artifacts:read
Path Parameters
Session id
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/sessions/497f6eca-6276-4993-bfeb-53cbbbba6f08/artifacts"[ { "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", "session_id": "1ffd059c-17ea-40a8-8aef-70fd0307db82", "size_bytes": 0, "version": 0 }]List a project's artifacts GET
Everything produced anywhere in the project, collapsed to each artifact's latest revision with a revision count. Newest first. Use `GET /v1/artifacts/{artifact_id}/versions` for an artifact's history.
Subscribe to account events GET
A live server-sent-event stream of everything happening in the account: artifacts appearing, jobs changing state, chats finishing, kanban card runs settling. This is the intended way to wait for dispatched work rather than polling. Each frame is a JSON object with a `type` discriminator and the new state inline — there is no need to re-read the resource to learn what changed. **The stream is not replayable.** It carries no event ids and ignores `Last-Event-ID`; anything produced while you were disconnected is not redelivered. On reconnect, re-read whatever you care about (`GET /v1/jobs`, `GET /v1/sessions/{id}/artifacts`) and carry on from there. Treat it as a latency optimization over polling, not as a durable log.