---
title: "Release a legal hold."
method: DELETE
path: "/api/holds/{reference}"
tags: ["Legal Holds"]
---

# Release a legal hold.

`DELETE /api/holds/{reference}`

Removes the hold with the given reference. Once released, evidence previously covered by this hold may become eligible for deletion or purge if no other holds remain. Releasing a hold is audited. Admins may release another user's hold via the owner parameter. Requires the `holds:write` scope.

## Path parameters

- `reference` string, required

## Query parameters

- `owner` string

## Headers

- `Authorization` string, required

## Response `200`

The hold was released.

## Other responses

- `400` — Bad Request
- `401` — The Authorization header is absent or the API key is not recognized.
- `404` — No hold with the given reference exists for this user.
- `413` — Content Too Large
- `415` — Unsupported Media Type
- `500` — Internal Server Error
- `503` — Service Unavailable

## Changes

- **2026-08-04** `ee79a60eea42` — 1 info
  - added the non-success response with the status `415`
- **2026-08-03** `e46672d44401` — 1 info
  - added the non-success response with the status `413`

[Change history](https://skmtc.dev/philterd/apis/philter-api/changes/api/holds/:reference/delete.md)

---

[API](https://skmtc.dev/philterd/apis/philter-api.md) · [All operations](https://skmtc.dev/philterd/apis/philter-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/philterd/philter-api/revisions/d90a12a66fa6/schema)