🎁 100 free AI Toolkit licenses – apply by August 15.Learn more

Import Markdown via REST API

Available in Start planBetav2.39.1

The Markdown import API converts .md files into Tiptap JSON format.

Review the postman collection

You can also experiment with the Document Conversion API by heading over to our Postman Collection.

Choose your region

The default endpoint api.tiptap.dev is served from the EU region. The conversion service is also available in the US region at api-us.tiptap.dev.

Import Markdown

POST /v2/convert/import/markdown

The /v2/convert/import/markdown endpoint converts Markdown files (.md or .markdown) into Tiptap's JSON format. Upload a file using multipart/form-data.

Example (cURL)

curl -X POST "https://api.tiptap.dev/v2/convert/import/markdown" \
    -H "Authorization: Bearer YOUR_TOKEN" \
    -F "file=@/path/to/file.md"

Subscription required

This endpoint requires a valid Tiptap subscription. For more details review our pricing page.

Required headers

NameDescription
AuthorizationThe JWT token to authenticate the request. Example: Bearer your-jwt-token

Body

NameTypeRequiredDescription
fileFileYesThe Markdown file to convert (.md or .markdown)
verbosestringNoLogging verbosity level (bitmask: 1=log, 2=warn, 4=error)

Response (200 OK)

{
  "data": {
    "content": {
      "type": "doc",
      "content": [
        {
          "type": "paragraph",
          "content": [
            {
              "type": "text",
              "text": "Hello from Markdown!"
            }
          ]
        }
      ]
    }
  },
  "logs": {
    "info": [],
    "warn": [],
    "error": []
  }
}

Error responses

StatusCodeDescription
400NO_FILE_PROVIDEDNo file was provided
400INVALID_FILE_TYPEFile is not .md or .markdown
422FAILED_TO_GET_FILE_ARRAY_BUFFERFailed to read file buffer
500FAILED_TO_CONVERT_MARKDOWN_TO_TIPTAP_JSONFailed to convert Markdown to JSON

Support & Limitations

Markdown import parses Markdown text into Tiptap JSON via the v2 cloud API. The endpoint supports standard CommonMark and GFM tables. Custom syntaxes used by optional Tiptap extensions (underline, highlight, math) are not parsed by the import service and won't appear in the returned JSON.

FeatureSupport
Text contentβœ“ Paragraphs, headings (1–6), hard breaks
Inline formattingβœ“ Bold, italic, strikethrough, inline code
Block elementsβœ“ Blockquotes, code blocks (fenced with language), horizontal rules
Listsβœ“ Bullet lists, ordered lists, task lists, nested lists
Tablesβœ“ Basic pipe-syntax tables (single header row, no merged cells)
Linksβœ“ Hyperlinks with text and URL
Imagesβœ“ Image references with alt text
Underlineβœ— Custom ++text++ syntax not registered on the server
Highlightβœ— Custom ==text== syntax not registered on the server
Text color / Fontβœ— No Markdown syntax for colors, font family, or font size
Text alignmentβœ— No Markdown syntax
Spacing / Indentationβœ— No Markdown syntax
Merged cellsβœ— Markdown tables don't support colspan or rowspan
Headers & Footersβœ— No concept in Markdown
Page layoutβœ— No page breaks, sections, or page size
Mathβœ— $...$ syntax not registered on the server
Footnotes & Endnotesβœ— Not supported in CommonMark

For the full DOCX feature comparison, see the Supported features matrix.