---
title: "Record that you went back and told them it was wrong"
method: POST
path: "/v2/workspaces/{id}/disclosures/{disclosure}/retracted-notice"
tags: ["Disclosures"]
---

# Record that you went back and told them it was wrong

`POST /v2/workspaces/{id}/disclosures/{disclosure}/retracted-notice`

## Request

- Base URL: `https://api.infolang.ai`
- URL: `https://api.infolang.ai/v2/workspaces/{id}/disclosures/{disclosure}/retracted-notice`
- Auth: one of:
  - HTTP bearer
  - HTTP bearer
  - HTTP bearer

COEXISTS with the disclosure it names and ERASES NOTHING. The original telling stays in `told` forever; the thread gains a mark saying a notice was given, and the current line is unchanged (a notice is not an amend).

Named `retracted-notice` and not `retract` on purpose: a telling cannot be taken back. The notice takes CONTENT rather than a flag because it is speech too, and it has a body somewhere.

Requires the `coord:write` scope. Accepts all three lanes: a session JWT (bounded by the caller's role on this workspace) or an `il_*` machine credential whose own scope set, workspace set and validity window cover it — both ceilings apply and neither can raise the other, so a credential carrying `coord:write` is still refused where the role does not permit it.

A credential with no scope record resolves to `LEGACY_DEFAULT`, which does NOT include `coord:write` — mint a key with it explicitly (`POST /v2/workspaces/{id}/keys`).

## Path parameters

- `id` string, required
- `disclosure` string, required

## Request body

- object
  - `reason` string, required
  - `memory_id` string
  - `notice` object
    - `space` 'memory' | 'assertion', required
    - `id` string, required

## Response `201`

The notice record

- object
  - `record` string, required
  - `authority` 'inference' | 'observation' | 'operator', required
  - `minted` string, nullable
  - `appended` boolean
  - `advisory` unknown
  - `folded_inert` boolean

## Other responses

- `401`: Missing/invalid credential, or `credential_expired` — the credential is outside its `[not_before, expires_at)` window and must be replaced
- `403`: `insufficient_scope` — the credential's own scope set, or the caller's role on this workspace, does not cover the scope this route requires (the missing scope is named in the message). Or `forbidden` — the credential is not scoped to this workspace, or holds no grant on it
- `501`: The disclosure verbs are not compiled into this deployment (`kernel-verbs` is off upstream)

---

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