List conversation attachments
Durable attachments (user uploads + sandbox outputs) for one conversation. Each entry carries a downloadUrl.
bearerAuthAuthorizationBearer <token>Personal API key (Authorization: Bearer pulse_...). Scoped to selected organizations (or all current ones); acts as the creating user. If the key covers more than one organization, pass its organizationId on each request.
id*stringorganizationId?stringOrganization to operate in. Optional when the API key is bound to exactly one organization (inferred). Required for keys that cover several or all organizations, and for session cookie auth.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidworkspaceId?stringDeprecatedDeprecated: the old name of organizationId, still accepted. If both are sent, they must match.
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$uuidAttachments for the conversation
application/json- response
items*array<>total*numbercurl -X GET 'https://pulse.bilby.ai/api/v1/conversations/string/attachments' \ -H 'Authorization: Bearer YOUR_API_KEY'{ "items": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "conversationId": "ee6e55e8-45fe-4a3e-9bc8-4669f9fdf77a", "messageId": "string", "filename": "string", "mediaType": "string", "byteSize": 0, "sourceKind": "string", "createdAt": "2019-08-24T14:15:22Z", "downloadUrl": "string" } ], "total": 0}Initialize file upload POST
Start a 2-phase upload. Returns a presigned `uploadUrl` (`PUT` file bytes with `Content-Type: <fileType>`) plus `objectKey` and short-lived `uploadToken`. Then send the message with `attachments: [{ objectKey, filename, mediaType, uploadToken }]`. Accepts the same files as a conversation in Bilby (images, PDF, Word, PowerPoint and Excel files, text/code, SVG). Max 25MB per file.
Get attachment download URL GET
Returns a short-lived signed `downloadUrl` (1h) for one durable attachment. Unlike the `readUrl` from `/attachments/init` (15m, temp key), this authorizes by attachment UUID against the committed `chats/` key — safe for bots to fetch server-side.

