# Change invoice notification

> Whether and how the account is told of a new invoice or credit note.

- Effect: Write - Changes the account. Agents ask first.
- Idempotent: yes
- Stability: beta
- MCP tool: `manitu_account_financialdocument_notification_set` on https://mcp.manitu.de/mcp
- REST: `POST https://api.manitu.de/v1/account/financialdocument/notification/set`
- Needs: `account`
- Page: /reference/account/financialdocument/notification/set/

**Changes the account. Agents say what will happen and wait for an explicit yes before calling it.**

## MCP tool

`manitu_account_financialdocument_notification_set`

### Description for the model

Sets how the manitu customer account this connection works in learns of a new invoice or credit note: type mail with mail_type info (a short note) or summary_and_pdf (a summary with the PDF attached), or type none (no mail; the documents stay in the customer panel). mail_type is required with mail and refused with none. Returns the settings as manitu_account_financialdocument_notification_get shows them. Refused per field: /mail_type required or not_for_type. Refused if this access may not change the account's base data.

### Arguments

- `type` (string, required) - How the account learns of a new invoice or credit note: mail - by mail to the billing address; none - not at all, the documents are in the customer panel only. (one of `"none"`, `"mail"`)
- `mail_type` (string | null) - For type mail only, else null: info - a short note; summary_and_pdf - a summary with the PDF attached. (one of `"info"`, `"summary_and_pdf"`, `null`)

### Example

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

## REST

`POST https://api.manitu.de/v1/account/financialdocument/notification/set`

### Authentication

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

### Request body

JSON; unknown fields are refused.

- `type` (string, required) - How the account learns of a new invoice or credit note: mail - by mail to the billing address; none - not at all, the documents are in the customer panel only. (one of `"none"`, `"mail"`)
- `mail_type` (string | null) - For type mail only, else null: info - a short note; summary_and_pdf - a summary with the PDF attached. (one of `"info"`, `"summary_and_pdf"`, `null`)

### Response

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

- `account_id` (integer, required) - The customer account - its id is also its customer number.
- `type` (string, required) - How the account learns of a new invoice or credit note: mail - by mail to the billing address; none - not at all, the documents are in the customer panel only. (one of `"none"`, `"mail"`)
- `mail_type` (string | null, required) - For type mail only, else null: info - a short note; summary_and_pdf - a summary with the PDF attached. (one of `"info"`, `"summary_and_pdf"`, `null`)

### Statuses

- `200` Success.
- `400` The request does not match the declared input schema.
- `401` No credential was presented, or it was not recognised.
- `403` The credential is not permitted to use this operation.
- `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/account/financialdocument/notification/set' \
  -H 'X-API-Key: $API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"type":"none"}'
```

## Example result

```json
{
  "account_id": 12345,
  "type": "none",
  "mail_type": "info"
}
```