---
title: "Clone a posture into an org"
method: POST
path: "/postures/{posture_id}/clone"
tags: ["Postures"]
---

# Clone a posture into an org

`POST /postures/{posture_id}/clone`

## Request

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

Copies the posture and its current revision into the target org's scope. Authorized: org_admin / org_owner of the destination org. Authorization: the caller must also be a member of the SOURCE posture's organization to read/copy it (platform-scoped catalog postures are clonable by any authenticated caller), so a `posture_id` in an org the caller does not belong to returns the same 404 as a nonexistent posture and cannot be exfiltrated.

## Path parameters

- `posture_id` string, required

## Headers

- `Idempotency-Key` string, required

## Request body

- object
  - `target_org_id` string, required: ID of the org that will own the cloned posture (the clone is created with scope=org).
  - `name` string: Optional override for the cloned posture's name.

## Response `201`

Posture.

- Posture: Trust posture row (mig 173). Library row; revisions are versioned bodies stored separately.
  - `posture_id` string, required
  - `slug` string, required: URL-safe identifier (e.g., 'standard', 'banking-core').
  - `name` string, required
  - `description` string, nullable
  - `scope` 'platform' | 'org', required
  - `org_id` string, nullable: NULL for platform-scope postures.
  - `owner_user_id` string, uuid, nullable
  - `is_default` boolean, required: True for Mnemom-shipped platform defaults.
  - `current_revision_id` string, nullable, required: FK to trust_posture_revisions; NULL only mid-create.
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required
  - `deleted_at` string, date-time, nullable: Soft-delete timestamp; NULL = live.

## 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)