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)

Method	Path	Purpose
POST	/v1/messages	Post a chat message to a list or an item

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

curl -X POST https://api.eu.liza.app/api/v1/messages \
  -H "Authorization: Bearer DEIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"list_item":"ITEM_ID","text":"Erledigt ✅"}'

Blocks (advanced)

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

Method	Path	Purpose
POST	/v1/blocks	Create a block/message
GET	/v1/blocks/{blockId}	Retrieve a block (UUID or SID)
POST	/v1/blocks/feed	Load the blocks of a context (channel/thread/item)
POST	/v1/blocks/load	Older blocks (cursor)
POST	/v1/blocks/next	Newer blocks
PATCH	/v1/blocks/{blockId}	Update a block (creator only)
DELETE	/v1/blocks/{blockId}	Delete a block (creator only)
POST	/v1/blocks/{blockId}/reactions	Toggle an emoji reaction

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

Field	Type	Required	Description
type	string (≤100)	✅	Block type (e.g. chat)
group_	UUID	✅	Group/channel context
text	string	–	Text (default "")
content	object | array	–	Structured content
list / list_item / channel / thread / parent / call	UUID	–	Context reference
mentions	UUID[]	–	Mentions
tags	string[]	–	Tags
scope	enum public|inherit|private	–	Visibility (default inherit)
color	#RRGGBB	–	Color
start_date / end_date	date (ISO)	–	Time range
askAI	boolean	–	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.