# Delete a notice from manitu

> Removes a notice of this access from the customer panel.

- Effect: Destructive - Removes something for good. Agents ask first.
- Idempotent: no
- Stability: stable
- MCP tool: `manitu_access_notice_delete` on https://mcp.manitu.de/mcp
- REST: `POST https://api.manitu.de/v1/access/notice/delete`
- Needs: `account_user`
- Counts against: [writes](/rate-limits/#limit-writes) (60 per hour per account)
- Page: /reference/access/notice/delete/

## MCP tool

`manitu_access_notice_delete`

**Removes something for good. Agents name what will be lost and wait for an explicit yes; a program should ask the same.**

### Description for the model

Removes a notice manitu left for the access this connection uses from the manitu customer panel, by its notice_id - the user cannot get it back. Only when the user asks for it; to stop it showing as new, [`manitu_access_notice_set`](/reference/access/notice/set.md) (read) is enough.

### Arguments

- `notice_id` (integer | string, required) - The notice_id of the notice. Never guess one. (pattern `"^[1-9][0-9]*$"`; minimum `1`)
- `approval_token` (string, write-only) - The token of the way call_again from the approval_required answer of the same call - only after the user said yes to everything in its elements. Valid 15 minutes, once. (minLength `1`; maxLength `255`)

### Example

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

## REST

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

**This request removes something.**

### Description

Removes a notice manitu left for the calling access in the customer panel, by its notice_id. The notice cannot be restored. Marking it read instead is [`POST /v1/access/notice/set`](/reference/access/notice/set.md). Made with a session of the customer panel, the call is carried out at once; otherwise the caller confirms it first: approval_required with the way call_again, then the same call again with its approval_token - unless the access is set to make such changes without asking.

### Authentication

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

### Request body

JSON; unknown fields are refused.

- `notice_id` (integer | string, required) - The notice_id of the notice. (pattern `"^[1-9][0-9]*$"`; minimum `1`)
- `approval_token` (string, write-only) - The token of the way call_again from the approval_required answer of the same call - only after the user said yes to everything in its elements. Valid 15 minutes, once. (minLength `1`; maxLength `255`)

### Response

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

- `notice_id` (integer, required)

### 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/delete' \
  -H "X-API-Key: $API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"notice_id":12345}'
```

## Example result

```json
{
  "notice_id": 12345
}
```
