Skip to main content
Correct 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

Body

application/json

Text edits, or corrected data

Correct the text in place. Only header, section, section field, context and markdown text can change; buttons, links and their behaviour stay as sent. Free.

revision
integer
required

The revision you read. If the message has changed since, nothing is changed and the answer is 409 revision_conflict.

Required range: x >= 0
edits
object[]
Maximum array length: 500
remove_blocks
integer[]

Positions of blocks to remove.

Maximum array length: 50
Required range: x >= 0
text
string

The notification text. Omitted, it is generated from the edited blocks.

Required string length: 1 - 4000

Response

The message, as it now reads

mode
enum<string>
required
Available options:
text,
rerender
credits_used
integer
required
message
object
required
remaining_credits
number | null