List Items

Two equivalent entry points: the flat resource /v1/list-items and the nested path under a specific list.

Method	Path	Purpose
`GET`	`/v1/list-items`	List items (pagination/filters)
`POST`	`/v1/list-items`	Create item
`GET`	`/v1/list-items/{itemId}`	Fetch item
`PATCH`	`/v1/list-items/{itemId}`	Update item
`DELETE`	`/v1/list-items/{itemId}`	Delete item (soft delete)
`GET`	`/v1/lists/{listId}/items`	Items of a list
`POST`	`/v1/lists/{listId}/items`	Create item in a list
`GET`	`/v1/me/agenda`	Compact agenda: due items + today's events

Query (`GET /v1/list-items`)

Pagination (page, pageSize, search) plus:

Parameter	Type	Description
`list`	UUID	by list
`status`	string	exact status
`priority`	number (1–10)	by priority
`assigned_to`	UUID	by assigned user
`includeArchived`	boolean (default `false`)	include archived
`includeTrashed`	boolean (default `false`)	include trash

REST vs. MCP

The convenience filters state, assigned_to_me, due_within_days, sort, and compact are only available on the MCP toollist_list_items — not in the REST API.

Agenda (`GET /v1/me/agenda`)

A compact daily overview in one call — meant for widgets and dashboards. Returns both: overdue and due-today items, plus today's remaining events (recurring events included).

Query	Type	Description
`list`	string	only entries of this list
`only_overdue`	boolean	only overdue, excluding items due today

Response:

json

{
  "due": [
    { "id": "…", "sid": "…", "text": "Prepare release",
      "list_id": "…", "list_sid": "…", "list_name": "Sprint 42",
      "target_date": "2026-08-30T00:00:00.000Z",
      "overdue": true, "days_overdue": 2 }
  ],
  "due_total": 7,
  "events": [ … ],
  "events_total": 3
}

The lists are capped at 10 entries; due_total and events_total carry the real totals so a counter does not compute against the truncated list.

Body — create (`POST /v1/list-items` or `/v1/lists/{listId}/items`)

Field	Type	Required	Description
`list`	UUID	✅*	Target list (*omitted on the nested path)
`text`	string (1–500)	✅	Title
`description`	string	–	Description
`status`	string	–	Status (see below)
`stage`	string	–	Workflow stage
`progress`	number (0–100)	–	Progress
`priority`	number (1–10)	–	Priority
`type`	string	–	Type
`scope`	enum `public`\|`private`\|`shared`	–	Visibility
`assigned_to`	UUID[]	–	Assignments
`responsible`	UUID \| null	–	Responsible person
`tags`	string[]	–	Tags
`target_date` / `start_date` / `end_date`	date (ISO) \| null	–	Dates
`time_allocated`	number ≥ 0	–	Time budget
`fields`	object	–	Custom fields
`parent`	UUID \| null	–	Parent item
`sort_key`	string	–	Sort key
`num` / `level`	integer	–	Numbering / level
`anchor`	UUID \| null	–	Item this item docks onto (info-/detail-column mechanism). Only controls which display layer the item appears in — `parent` remains the real hierarchy. Set both when creating a child item of such a column.
`layer`	integer ≥ 0	–	Display layer for the `anchor` mechanism (0 = main list). Only meaningful together with `anchor`.
`content`	object \| array \| string	–	Structured content payload (e.g. box-type-specific data). Objects/arrays are stored as JSON.

Body — update (`PATCH /v1/list-items/{itemId}`)

Same as create (all optional, without list), plus archived (boolean).

Status: open = ""/todo/open/in_progress; done = done/completed.

Example

bash

# Open items of a list
curl "https://api.eu.liza.app/api/v1/lists/LIST_ID/items?includeArchived=false" \
  -H "Authorization: Bearer DEIN_TOKEN"

# Create an item
curl -X POST https://api.eu.liza.app/api/v1/lists/LIST_ID/items \
  -H "Authorization: Bearer DEIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"text":"Release vorbereiten","priority":7,"target_date":"2026-07-10"}'

List Items ​

Query (GET /v1/list-items) ​

Agenda (GET /v1/me/agenda) ​

Body — create (POST /v1/list-items or /v1/lists/{listId}/items) ​