# DELETE /api/v2/work-item-links/{work_item_link}

Delete a work item link

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

Permanently unlinks two work items and answers `204`, like the "remove linked item" action in plnnrly.

There is no soft delete, no ?force parameter and no restore verb, and there is no PATCH either: to change a relationship, DELETE the link and POST a new one to `work-items/{work_item}/links`. Neither work item is otherwise affected. Links are hard-deleted and leave no tombstone, so retrying a delete that already succeeded answers `404` rather than `204`; treat that as success.

## Parameters
- work_item_link (integer, path): The WorkItemLink'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/work-item-links/1' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'
```