Skip to main content
Delete a sent message

Authorizations

Authorization
string
header
required

LithoBlocks API key obtained from your organization dashboard. The LithoBlocks MCP server also presents a Supabase-issued user session token here on the user's behalf; such a token acts as that user with the scopes their organization role allows.

Headers

Idempotency-Key
string

Any unique string (a UUID is fine). Repeating a request with the same key and body within 24 hours replays the original response with Idempotency-Replayed: true instead of running again; the same key with a different body is a 409. Incomplete and 5xx outcomes are retained for reconciliation beyond 24 hours. Applies only on the documented endpoints. Never automatically change keys to bypass an uncertain outcome.

Required string length: 1 - 255
Example:

"3f7d2c1a-9b4e-4f0a-8c6d-2e1b5a7c9d10"

Path Parameters

id
string<uuid>
required

Query Parameters

revision
integer | null

The revision you read. If the message has changed since, nothing is deleted and the answer is 409 revision_conflict. Omit to delete whatever the message now says.

Required range: x >= 0
scrub
enum<string>

true also clears LithoBlocks' stored copy of what the message said (its blocks, metadata, notification text and the send's logged input). The record and its history stay.

Available options:
true,
false

Response

The message was deleted, or already had been

outcome
enum<string>
required
Available options:
deleted,
already_deleted
scrubbed
boolean
required

Whether LithoBlocks' stored copy is now cleared.

message
object
required