---
title: "Take a waiver back"
method: DELETE
path: "/v1/intakes/{id}/items/{key}/waive"
tags: ["Intakes"]
---

# Take a waiver back

`DELETE /v1/intakes/{id}/items/{key}/waive`

## Request

- Base URL: `https://api.briefgate.dev`
- URL: `https://api.briefgate.dev/v1/intakes/{id}/items/{key}/waive`
- Auth: HTTP bearer

Undo a waiver and put the item back to `pending`. This is a fresh start, not an undo of the earlier state: the previous value, submission and revision note are discarded along with the waiver itself, because the client has to be asked again either way. If this was the last thing keeping a completed intake finished, the intake reopens to `in_progress`.

## Path parameters

- `id` string, required
- `key` string, required

## Response `200`

Waiver reverted; item is pending again

- object
  - `item` object
    - `key` string
    - `type` string
    - `assignee` 'client' | 'owner'
    - `label` string
    - `required` boolean
    - `status` 'pending' | 'submitted' | 'needs_revision' | 'approved' | 'waived'
    - `waiver` object
      - `state` 'none' | 'proposed' | 'waived'
      - `reason` string, nullable
      - `requested_by` 'client' | 'owner', nullable
      - `requested_at` string, date-time, nullable
      - `decided_at` string, date-time, nullable
    - `received_outside` boolean: True once the owner settled this item through POST .../received-outside instead of the client submitting it through the portal. `value` was never actually supplied by the client when this is true — check it before trusting `value` as a genuine answer.
    - `received_outside_note` string, nullable: The owner's own note on how/when this was received, from POST .../received-outside.
    - `client_note` string, nullable: Written by the client. Visible to both sides.
    - `owner_note` string, nullable: The owner's own note on this item. Never shown to the client.
    - `files` object[]
      - `id` string
      - `filename` string
      - `mime` string
      - `size` integer
      - `width` integer, nullable
      - `height` integer, nullable
      - `av_status` 'pending' | 'clean' | 'infected' | 'error' | 'skipped'
      - `checksum_sha256` string, nullable: SHA-256 of the stored bytes, for verifying a download.

## Other responses

- `401`: Missing or invalid API key
- `403`: Authenticated but not allowed to perform this action
- `404`: Resource not found
- `409`: The item is not currently waived

---

[API](https://skmtc.dev/briefgate/apis/briefgate-api.md) · [All operations](https://skmtc.dev/briefgate/apis/briefgate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/briefgate/apis/briefgate-api/revisions/b21afed4748b?raw)
