Resolve chat attachments
POST /users/me/chat-sessions/attachments finds Leni AI file anchors in chat.message_response.summary, collects data-file-id values (HTML attributes, JSON-like strings, and structured summary arrays), then calls Leni POST /resolve-file-url for each id. Successful resolutions return presigned http(s) URLs; otherwise the original file id string is returned for that slot.
POST
/users/me/chat-sessions/attachmentsContent-Type: application/json. Body matches ChatSessionScopedBodyDto (same shape as Message responses).
JSON body
request| Field | Type | Required | Description |
|---|---|---|---|
| sessionId | string (UUID) | Required | The chat session to read from. You must already have at least one message in this session as the API key owner. |
| messageId | string (UUID) | Optional | Optional. When set, only file anchors from that message are resolved. The message must belong to you and exist in sessionId. Omit, or send empty or whitespace-only, to resolve files across the entire session. |
Example request
{
"sessionId": "00000000-0000-0000-0000-000000000000",
"messageId": "00000000-0000-0000-0000-000000000001"
}Response
responseResponseResponse shape
{
"sessionId",
"messageId": <uuid or null>,
"messageResponses": [
{ "data-file-id": "<url or id>" },
...
]
}