---
title: "Retire a saved Watch"
method: POST
path: "/api/v1/watches/{id}"
tags: ["Watches"]
---

# Retire a saved Watch

`POST /api/v1/watches/{id}`

## Request

- Base URL: `https://api.signalbureau.ai`
- URL: `https://api.signalbureau.ai/api/v1/watches/{id}`
- Auth: none declared. Required headers: `x-api-key`

Body `{"action":"retire"}`. The Watch stops being recallable and its paid slot is freed. Nothing is deleted: its versions and deliveries are kept. Same content as the MCP tool `retire_watch`.

## Path parameters

- `id` string, required

## Headers

- `x-api-key` string, required

## Request body

- object
  - `action` 'retire', required

## Response `200`

Retired.

- object

## Other responses

- `400`: bad-request: `action` is not `retire`; the body names the accepted value.
- `401`: No key: `{state: "key-required", error, howToGetOne}`. Configuring and unfurling need no key; saving, listing, recalling and retiring do.
- `403`: not-yours: the Watch is held by a different key and was not shared with this one; nothing was read, changed or charged.
- `404`: not-found: `{state: "not-found", watchId}` — no Watch with that id is saved to your key.
- `409`: retired or conflict: the Watch is already retired, or the change conflicts with its current state; the body states the reason.
- `429`: slow-down: past the published burst limit for this door. The `retry-after` header gives the seconds to wait.
- `503`: cannot-verify: we could not confirm the Watch is yours (key or Watch store did not answer, or the record names no owner); refused, retry shortly.

---

[API](https://skmtc.dev/sigb/apis/signal-bureau-api.md) · [All operations](https://skmtc.dev/sigb/apis/signal-bureau-api/llms.txt) · [OpenAPI document](https://skmtc.dev/sigb/apis/signal-bureau-api/revisions/290c9c6ca0d0?raw)