API Docs
Beta · updated November 17, 2026
Authentication
Send your API key as a bearer token on every request. Keys start with rd_.
Authorization: Bearer rd_your_api_key
Render
POST /v1/render — turns one input into a PDF or PNG file. Exactly one of markdown, html, url, or template is required.
curl -X POST https://api.renderdock.dev/v1/render \
-H "Authorization: Bearer rd_your_api_key" \
-H "Content-Type: application/json" \
-d '{"markdown": "# Weekly report\n\nShipped the queue.", "format": "pdf"}' \
-o weekly-report.pdf
Request fields
markdown
string — Markdown source, rendered with the Report print theme
html
string — raw HTML
url
string — public http(s) URL; private addresses are blocked
template
string — Handlebars template, merged with data
data
object — data merged into template
format
pdf (default) or png
paper
PDF page size: A4 (default), Letter, Legal, A3
width / height
PNG viewport in px (default 1280×900)
filename
base name for Content-Disposition (without extension)
Template example
curl -X POST https://api.renderdock.dev/v1/render \
-H "Authorization: Bearer rd_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"template": "<h1>Invoice for {{company}}</h1><p>{{amount}}</p>",
"data": { "company": "Acme GmbH", "amount": "€120.00" },
"format": "pdf",
"filename": "invoice-acme"
}' \
-o invoice.pdf
Responses
Success returns the file with the matching content type (application/pdf or image/png) and an X-RenderDock-Quota header like 12/200 showing used/total monthly renders.
Errors
400
invalid input, blocked URL, or unsupported format
401
missing or invalid API key
402
monthly quota exceeded
429
rate limit (30 renders per minute per key)
500
render failed on our side
Limits
- Free tier: 200 renders per month, resetting on the first of the month
- Request body: 5 MB · render timeout: 15 s (URLs)
- Rate limit: 30 renders per minute per key
MCP server
Give your agent a render tool:
npx @renderdock/mcp
Configuration: RENDERDOCK_API_KEY (required) and RENDERDOCK_API_URL (optional). The tool returns the local path of the written file, or base64 with response_mode: base64.
n8n node
Install the community node in n8n (Settings → Community Nodes), then add a RenderDock node to any workflow:
npm install n8n-nodes-renderdock
Security
URL rendering resolves DNS first and refuses private, loopback, and link-local addresses. Credentials in URLs are rejected. Rendered content is processed transiently and not stored.