Skip to main content
POST
Validate a document JSON

Authorizations

Authorization
string
header
required

Short-lived, Developer-API-audience token obtained by the trusted MCP service through token exchange (mcp_at_...). Raw MCP resource tokens are rejected.

Query Parameters

strict
boolean

Enable strict validation mode (validates anchors, references, citations, abbreviations, and footnotes)

Body

application/json
config
object
required

Complete document JSON following the Autype document schema. Must include document (with type) and sections. May also include variables, defaults, abbreviations, citations, footnotes, and style — all at the same level inside this object. The output format is determined by the document.type field (pdf, docx, or odt). Variable placeholders can use either {{varName}} or ${varName} syntax — both are accepted on input. See the Document JSON Syntax docs for the full schema reference.

Example:
pdfProfile
enum<string>
default:standard

PDF output profile. Only valid for PDF output. PDF/A and PDF/UA profiles flatten interactive form fields to preserve the selected profile.

Available options:
standard,
pdfa-1b,
pdfa-2b,
pdfa-3b,
pdfua-1
webhook
object

Optional webhook configuration. Receives a POST when the job completes or fails.

Response

Validation result

valid
boolean
required

Whether the document JSON is valid

errors
object[]

Validation errors (present when valid is false)

warnings
object[]

Validation warnings (non-blocking issues found in non-strict mode)