Skip to main content
The document JSON is the core data structure used by the Render endpoint (POST /render) and Bulk Render endpoint (POST /bulk-render) to generate PDF, DOCX, and ODT documents.

Top-level structure

A document JSON object has the following top-level keys:

Style presets

For API and MCP workflows, you can reference an organization-wide style preset instead of embedding a large defaults object in every request:
Style presets are resolved server-side. If both stylePresetId and inline defaults are provided, Autype merges them and lets inline defaults win. Built-in references never create database style rows; use the explicit Customize action when you need an editable workspace copy. This keeps JSON and Markdown requests compact while preserving the full JSON schema for advanced clients.

Strict validation mode

The render endpoints (POST /render and POST /render/markdown) support an optional ?strict=true query parameter that enables strict validation. In strict mode, the API performs additional checks that go beyond schema validation:
  • Broken internal references — references to non-existent anchors (e.g., [see here](#missing-anchor)) cause an error
  • Undefined citations@[citeKey] references to citation IDs not present in the citations array cause an error
  • Undefined abbreviations~ABK~ references to abbreviation keys not present in the abbreviations object cause an error
  • Undefined footnotes — every [^id] reference must have exactly one non-empty definition in footnotes
  • Duplicate anchors — multiple elements defining the same anchor ID cause an error (this is always checked, even without strict mode)
Without strict mode, broken references, undefined citations, and undefined abbreviations are treated as warnings and do not block rendering. With strict mode enabled, they become errors and the render request is rejected with a 400 Bad Request response containing the list of validation errors.
Strict mode is recommended for production workflows to catch issues early. In the Autype editor, these same checks are shown as warnings in the sidebar.

Document settings

The document object configures the page layout and document metadata.

Properties

Sections

Sections are the content containers of your document. There are two types:

Flow section

Flowing content that spans multiple pages automatically. This is the most common section type.

Columns

Page section

A single positioned page — useful for cover pages, title pages, or any content that needs precise vertical positioning.

Complete example

Next steps

Variables

Dynamic content substitution with text, number, image, list, and table variables.

Abbreviations

Define abbreviation short forms and generate abbreviation lists.

Citations

CSL-JSON citations and automatic bibliography generation.

Footnotes

Automatically numbered notes with editable Markdown definitions.

Defaults

Global styling: fonts, colors, spacing, header/footer, and more.

Layout

Flow and page sections, columns, page breaks, and spacers.

Text Elements

Headings, paragraphs, inline formatting, and anchors.

Tables

Tables with headers, rows, widths, alignment, images, form fields, captions, and data binding.

Form Fields

Standalone and table-cell controls with variable binding, styling, and PDF AcroForms.

Lists

Ordered and unordered lists with nested items.

Media & Code

Images, charts, QR codes, code blocks, and math equations.

Indices

Table of contents, list of figures, list of tables.