## Delete an item for good (tenant:forge:write and maintainer, or tenant:forge:admin)

`DELETE /api/forge/v1/projects/{key}/items/{number}`

Module: Forge · operationId: `deleteForgeItem` · Tag: Items · Auth: access token (`Authorization: Bearer <accessToken>`)

Requires `tenant:forge:admin`, or `tenant:forge:write` and project role maintainer or admin. An item with children is refused (409 `has_children`), so is one with a handoff still being delivered (409 `handoff_pending`) or a pending conversion (409 `conversion_pending`). Writes `forge.item.deleted` before the item goes; links, comments and sections go with it.

### Parameters

| Name | In | Type | Required | Description |
|---|---|---|---|---|
| `key` | path | string | yes | Project key (e.g. APP) |
| `number` | path | integer | yes | Item number in the project (12 of APP-12) |

### Responses

- **204** Deleted
- **403** Error (`application/json`)
- **404** Error (`application/json`)
- **409** Error (`application/json`)

### Example request

```bash
curl -X DELETE 'https://api.mbcom.cloud/api/forge/v1/projects/string/items/1' \
  -H "Authorization: Bearer $ACCESS_TOKEN"
```
