# DELETE /api/v2/subtasks/{subtask}

Delete a subtask

- MCP id: subtasks.destroy
- Scope: api:destroy:project_management
- Permission: project_management::manage_work_items
- Rate cost: 1 unit, write bucket.
- Cache-Control: private, no-store

Permanently deletes one checklist subtask and answers `204`.

There is no soft delete, no ?force parameter and no restore verb: a subtask comes back only by being re-created through `POST work-items/{work_item}/subtasks`, and it is appended to the end of the checklist rather than to its old position. Nothing else is deleted, except that any files attached to the subtask in plnnrly are removed with it.

## Parameters
- subtask (integer, path): The Subtask's numeric id.
- X-Request-Id (header, optional): A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
- If-Match (header, optional): The ETag a write is conditional on. A stale validator is 412 precondition-failed.

## Response 204

## Errors
- 403 forbidden-by-policy | insufficient-permission | insufficient-token-scope: Forbidden.
- 412 precondition-failed: Precondition failed.
- 400 idempotency-key-required | invalid-cursor | invalid-query-parameter | malformed-request | unsupported-parameter: Bad request.
- 401 token-expired | unauthenticated: Unauthenticated.
- 404 endpoint-not-found | resource-not-found: Not found.
- 406 not-acceptable: Not acceptable.
- 429 rate-limit-exceeded: Too many requests.
- 500 internal-error: Server error.
- 503 tenant-unavailable: Service unavailable.

## Example
```bash
curl -X DELETE \
  'https://<your-url>/api/v2/subtasks/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'
```