Skip to main content
Reschedule or edit a scheduled 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.

Path Parameters

id
string<uuid>
required

Body

application/json

Fields to change

data
object
destination
object
schedule
object
recurrence
object | null

null removes the recurrence

delivery_conditions
object | null

null removes the conditions

follow_live
boolean

true removes the pin, so the message sends whatever version is live at send time. false pins it to the version live now (re-pin). Omitted, the pin is unchanged

expiration
object

Expire the message: replace it with a notice, or delete it. Precise to about a minute; a button clicked after the deadline does nothing even before the message is replaced.

Response

Updated

id
string
required
status
enum<string>
required
Available options:
scheduled,
processing,
sent,
failed,
cancelled,
expired
template_id
string | null
required
template_version_id
string | null
required

The version this message is pinned to. null sends whatever version is live when it sends (follow_live); a legacy policy-driven message with no pin of its own uses its policy's

queue_policy_id
string | null
required

Set on legacy policy-driven messages only

destination
object
required
data
object
required
schedule
object
required
recurrence
object | null
required
repeat_count
integer
required
delivery_conditions
object | null
required
max_delay_at
string | null
required
expiration
object | null
required

The schedule's own expiry for each message it sends; the template's default and maximum apply too

source
string
required
error_message
string | null
required
created_at
string
required
processed_at
string | null
required