## Change status and tags of several addresses (tenant:masterdata:write)

`POST /api/masterdata/addresses:batchUpdate`

Module: Master data · operationId: `batchUpdateAddresses` · Tag: Addresses · Auth: access token (`Authorization: Bearer <accessToken>`)

Sets `statusCode` and/or adds and removes tags on up to 200 addresses. Every id is updated on
its own, exactly like a single `PUT` (status validation, the platform guard that answers `409`
for a customer with active tenants, events and version bump), so one failing id does not stop
the others. The answer is always `200` with one result per id, in request order; a failed id
carries `error.status` (`404` for unknown ids and ids of other tenants, `409`, `400`) and a
German `error.message`.

### Request body

`application/json` (required)

- `ids` (array of string (uuid), required): Addresses to change (each updated on its own)
- `addTags` (array of string): Tags to add
- `removeTags` (array of string): Tags to remove
- `statusCode` (string): New status (lookup `address-statuses`); the roles follow from it

Example:

```json
{
  "addTags": [
    "Messe 2026"
  ],
  "ids": [
    "0b6f6c1e-7d2a-4f0e-9a58-3c1f2b7d9e10"
  ],
  "removeTags": [],
  "statusCode": "INTERESSENT"
}
```

### Responses

- **200** One result per id (`application/json`)
- **400** Malformed body or query parameter (`application/json`)
- **401** Missing, invalid or expired token (empty body)
- **403** The token lacks the permission or carries no tenant (`application/json`)

Fields of the 200 answer:

- `results` (array of object, required): One result per id, in request order
  - `id` (string, required): The id of the request
  - `ok` (boolean, required): The update of this id succeeded
  - `error` (object): Why the update of this id failed (absent when `ok`)
    - `message` (string, required): German message
    - `status` (integer, required): HTTP status the single update would have answered (400, 404, 409)
    - `code` (string): Error code the single update would have answered (`invalid`, `not_found`, `version_conflict`, …)

Example 200 answer:

```json
{
  "results": [
    {
      "id": "3c5e7a9c-1d3f-4b5a-9c7e-1a3c5e7a9c1e",
      "ok": true
    },
    {
      "error": {
        "code": "not_found",
        "message": "Adresse nicht gefunden.",
        "status": 404
      },
      "id": "0b6f6c1e-7d2a-4f0e-9a58-3c1f2b7d9e10",
      "ok": false
    }
  ]
}
```

### Example request

```bash
curl -X POST 'https://api.mbcom.cloud/api/masterdata/addresses:batchUpdate' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"addTags":["Messe 2026"],"ids":["0b6f6c1e-7d2a-4f0e-9a58-3c1f2b7d9e10"],"removeTags":[],"statusCode":"INTERESSENT"}'
```
