# List notices from manitu

> What manitu left for this access in the customer panel - unread ones, or all.

- Effect: Read - Changes nothing.
- Idempotent: yes
- Stability: stable
- MCP tool: `manitu_access_notice_list` on https://mcp.manitu.de/mcp
- REST: `POST https://api.manitu.de/v1/access/notice/list`
- Needs: `account_user`
- Page: /reference/access/notice/list/

## MCP tool

`manitu_access_notice_list`

### Description for the model

Lists the notices manitu left for the access this connection uses, in the manitu customer panel (notices about services, invoices, security) - only the unread ones unless include_read, without their text: [`manitu_access_notice_get`](/reference/access/notice/get.md) has it. Urgent ones are about something the user should do soon - mention them. It changes nothing, not even read status.

### Arguments

- `include_read` (boolean) - true: read ones too; left out or false: only the unread ones.

### Example

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "manitu_access_notice_list",
    "arguments": {}
  }
}
```

## REST

`POST https://api.manitu.de/v1/access/notice/list`

### Description

Lists the notices manitu left for the calling access in the customer panel - about services, invoices or security -, without their text: only the unread ones unless include_read is true. Each says whether it is urgent. The text of one is [`POST /v1/access/notice/get`](/reference/access/notice/get.md). Changes nothing, not even whether a notice is read.

### Authentication

One of `X-API-Key`, `Authorization: Bearer …` - never more than one in a request.

### Request body

JSON; unknown fields are refused.

- `include_read` (boolean) - true: read ones too; left out or false: only the unread ones.

### Response

In `data`; the rest of the body as on every call.

- `notice_list` (array of object, required)
  - `notice_list[].notice_id` (integer, required)
  - `notice_list[].status` (string, required) - new: not read yet; read: marked as read (opened in the panel, or set); deleted is never listed. (one of `"new"`, `"read"`, `"deleted"`)
  - `notice_list[].priority` (string, required) - urgent: the user should read it soon - it is about something that needs doing. (one of `"normal"`, `"urgent"`)
  - `notice_list[].subject` (string | null, required)
  - `notice_list[].created_at` (string | null, required) - (format `date-time`)
  - `notice_list[].read_at` (string | null, required) - When it was first read; it stays when set back to new. (format `date-time`)
- `count_new` (integer, required) - Unread notices.
- `count_new_urgent` (integer, required) - Unread urgent notices.

### Statuses

- `200` Success.
- `400` The input is wrong, or the request itself (INVALID_INPUT). Each entry names its field and its reason - correct the input and call again.
- `401` No credential was presented, or it was not recognised (UNAUTHENTICATED).
- `403` The credential is valid, but may not do this (PERMISSION_DENIED). The reason says why - another credential is the way, not a repeat.
- `429` Too many calls. The Retry-After header says when to try again.
- `500` The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.
- `503` The channel this operation forwards through is unavailable.

### Example

```sh
curl -X POST \
  'https://api.manitu.de/v1/access/notice/list' \
  -H "X-API-Key: $API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{}'
```

## Example result

```json
{
  "notice_list": [
    {
      "notice_id": 12345,
      "status": "new",
      "priority": "normal",
      "subject": "string",
      "created_at": "2026-10-23T12:00:00+02:00",
      "read_at": "2026-10-23T12:00:00+02:00"
    }
  ],
  "count_new": 1,
  "count_new_urgent": 1
}
```
