---
title: "Soft-delete a posture"
method: DELETE
path: "/postures/{posture_id}"
tags: ["Postures"]
---

# Soft-delete a posture

`DELETE /postures/{posture_id}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/postures/{posture_id}`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Sets deleted_at; revisions retained for audit. Authorization: only an owner/admin of the organization that owns the posture may delete (a member with a lower role receives 403); a `posture_id` in an org the caller does not belong to returns the same 404 as a nonexistent posture, so the status never reveals that another tenant's posture exists.

## Path parameters

- `posture_id` string, required

## Headers

- `Idempotency-Key` string, required

## Response `200`

Soft-deleted (sets deleted_at; revisions retained for audit).

- object
  - `posture_id` string, required
  - `deleted` true, required

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `409`: Resource conflict — the request cannot proceed because of a current state conflict (e.g., resource already exists, version mismatch, in-flight idempotency key with a different body).
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

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