## Delete an unused lookup entry (tenant:settings:write)

`DELETE /api/masterdata/lookups/{kind}/{code}`

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

An entry still used by addresses or articles answers `409`; deactivate it (`isActive` false) instead. Emits `masterdata.lookup.updated`.

### Parameters

| Name | In | Type | Required | Description |
|---|---|---|---|---|
| `kind` | path | LookupKind | yes | Parameter table (one of `address-statuses`, `currencies`, `industries`, `payment-methods`, `payment-terms`, `salutations`, `shipping-types`, `tax-keys`, `units`) |
| `code` | path | string | yes | Entry code (`^[A-Za-z0-9_.-]{1,32}$`, stored upper-case), for `currencies` an ISO 4217 code |

### Responses

- **204** Deleted
- **400** Invalid input (`invalid`); `field` names the first, `details.fields` each invalid field (`application/json`)
- **401** Missing, invalid or expired token (empty body)
- **403** The token lacks the permission or carries no tenant (`application/json`)
- **404** Not found in the caller's tenant (or merged, see `code`) (`application/json`)
- **409** Stale version or conflict with existing data (`application/json`)

### Example request

```bash
curl -X DELETE 'https://api.mbcom.cloud/api/masterdata/lookups/address-statuses/NETTO30' \
  -H "Authorization: Bearer $ACCESS_TOKEN"
```
