Messages / Blocks

Last updated 24 days ago

Messages / Blocks ​

Chat and message content in Liza is made up of "Blocks". For simple message posting, there is also a convenient endpoint.

Post a message (simple) ​

MethodPathPurpose
POST/v1/messagesPost a chat message to a list or an item

Body: { "list": "<listId>" } or { "list_item": "<itemId>" } plus text.

bash

Blocks (advanced) ​

Base path: /v1/blocks. Fine-grained control over chat and thread content.

MethodPathPurpose
POST/v1/blocksCreate a block/message
GET/v1/blocks/{blockId}Retrieve a block (UUID or SID)
POST/v1/blocks/feedLoad the blocks of a context (channel/thread/item)
POST/v1/blocks/loadOlder blocks (cursor)
POST/v1/blocks/nextNewer blocks
PATCH/v1/blocks/{blockId}Update a block (creator only)
DELETE/v1/blocks/{blockId}Delete a block (creator only)
POST/v1/blocks/{blockId}/reactionsToggle an emoji reaction

Body — create a block (POST /v1/blocks) ​

FieldTypeRequiredDescription
typestring (≤100)✅Block type (e.g. chat)
group_UUID✅Group/channel context
textstring–Text (default "")
contentobject | array–Structured content
list / list_item / channel / thread / parent / callUUID–Context reference
mentionsUUID[]–Mentions
tagsstring[]–Tags
scopeenum public|inherit|private–Visibility (default inherit)
color#RRGGBB–Color
start_date / end_datedate (ISO)–Time range
askAIboolean–Request an AI reply (default false)

reactions expects { emoji, group_ }. Pure view endpoints (feed/load/next) take context IDs + size.

TIP

For simply "attaching a comment to an item", POST /v1/messages is enough, or the post_chat_message tool in MCP. The /v1/blocks endpoints are for clients that render entire chat feeds.