Skip to main content
Activate template version

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
version_id
string<uuid>
required

Body

application/json
expected_current_version_id
string<uuid>

Activate only if this is still the live version

note
string

Why; recorded with the activation

Maximum string length: 500

Response

Version activated

success
boolean
required
message
string
required
current_version
object
required
previous_version_id
string | null
required

The version that was live before; equal to current_version.id when nothing changed

changed
boolean
required

False when the version was already live

activation_id
string | null
required

The activation record; null when nothing changed