Skip to main content
Expire every message with a reference

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"

Body

application/json

The reference, and how they expire

reference
string
required

Every live message your sends tagged with this reference.

Required string length: 1 - 255
mode
enum<string>

Defaults to the pending expiry's mode, else replace.

Available options:
replace,
delete
retain_content
boolean

Defaults to the pending expiry's choice, else false: LithoBlocks' copies are cleared.

Response

The messages now due to expire

scheduled
integer
required

Messages due to expire now. Each is replaced within about a minute; their buttons stop working at once.

not_permitted
integer
required

Messages carrying the reference that a member did not send, and so left alone.

message_ids
string<uuid>[]
required