Skip to main content
POST
Validate blocks without saving

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.

Body

application/json

Blocks to validate

blocks
object[]
required
Minimum array length: 1
sample_data
object

Data to compile against; defaults to a null-filled skeleton of the request format

Response

Validation result

valid
boolean
required
request_format
object
required

{ template_id, data } where data holds null per placeholder and [{ field: null }] per array path; what a caller of compile/send must supply. GET /templates/{id}/input-schema describes the same paths with types, labels and nesting

blocks
object[]
required

The blocks as they would be stored: ids and action ids filled in

errors
object[]

Present when valid is false

compiled_preview
object[]

Slack Block Kit output for sample_data; present when valid is true

interactivity
object
fields_truncated
number

How many text fields were shortened to fit Slack's limits

warnings
string[]

What compile normalised: chart points filled with 0, series or points truncated to Slack's counts