Skip to main content
POST
Attach a file to a chat

Headers

X-Memloom-Owner
string<uuid>

The owner this request acts for. Applies to every owner-scoped endpoint, reads as well as writes. Omit it and the daemon's own default owner answers (see GET /health), which is what a single-owner install has always used. A value that is not a uuid is refused with 400 rather than coerced.

Body

application/json
filename
string
required
Example:

"brief.pdf"

contentBase64
string
required
sessionId
string<uuid>

The chat to attach to; omit to create one.

Response

The ingest outcome plus the session it landed in.

sessionId
string<uuid>
documentId
string<uuid>
outcome
enum<string>
Available options:
added,
updated,
unchanged,
converted,
exists
title
string
chunks
integer