Skip to main content
DELETE
Discard one of your draft review findings

Authorizations

Authorization
string
header
required

MeshQu API key passed as a bearer token: Authorization: Bearer mqu_…. Mint one in the console (Settings → API keys).

X-MeshQu-Tenant-Id
string
header
required

Tenant UUID for multi-tenant isolation. Required on all authenticated routes — validated before authentication (middleware/tenant.ts), so a missing or non-UUID header returns 400 (MISSING_TENANT_ID / INVALID_TENANT_ID) before the API key is checked.

Path Parameters

id
string<uuid>
required

Policy id. The submission must belong to it, or the request is a 404.

submissionId
string<uuid>
required

The sealed submission the note is about. This is the review IDENTITY — not the policy version, which is a mutable container that yields many sealed subjects over time.

draftId
string
required

The reviewer client's own handle for this note, in the same spelling a review record's item id uses. Client-issued: the server does not mint it, and it is unique only within one owner's notes on one subject. It is the SAME id the item will carry if the note is later recorded, so the link between a note and the item it became is legible without a pointer from the immutable side.

Pattern: ^[A-Za-z0-9._:-]{1,200}$

Response

The note is gone. A hard delete is permitted precisely because a working note is not evidence; nothing in the review record is touched, and any record already written stays exactly as it was.

The note is gone. A hard delete is permitted precisely because a working note is not evidence; nothing in the review record is touched, and any record already written stays exactly as it was.

id
string
required
deleted
boolean
required