POST /revisions/:id/data/command (Command: post_session_thread_item)
Request Body
Response
Returns the persisted item with server-stampedid, created_at, user_id, and the original/derived
fields.
The command raises thread.item_posted on the session’s stream, with the thread’s alias in its object block and the
item’s id, user_id and optional parent_id, type, role, source and client in its item block. A client
sent with the request is stored: the item in a listing, in
Get Session Thread Item and in the event’s item block all
carry the same value as source.client. See Types.
Errors
invalid_thread_envelope— the alias does not exist or itsvalue.typeis not"thread".thread_item_too_large— the serialized item exceedsworkflow.thread_item_bytes, 65,536 bytes (64 KiB). The body carrieslimit.invalid_request_body— a content block has an unknowntype, or afileblock omits one ofalias,name,content_type, orsize; both are rejected by request-schema validation before the command runs.invalid_thread_item_content— afileblock carries nofileobject at all, or itsaliasis outside the session-object alias grammar.too_many_files— the item contains morefilecontent blocks thanworkflow.thread_item_filesallows, 10. The body carrieslimit.file_not_found— afileblock references an alias that does not exist as a file object in the session.
Example
See also
- BlobHub Worker — thread items — how the worker
structures
contentandmetadatafor agent emissions, and the 60 KiB truncation behavior. - File session object — the object a
fileblock’saliasmust reference. - Upload Session File — the only way to create a
fileobject and obtain a validaliasfor it.

