Visual PDF templates + rendering API
Design PDFs visually. Ship them with one API call.
Build reusable templates in the visual Studio, or with the AI assistant and MCP server. Bind live data and render production-ready PDFs from your application.
No credit card required
Node.js · Python · REST
AI assistant · MCP server
200 OK
842 ms
186 kB
One template. Every document.
Change the data. Keep the design.
Dynamic templates bind JSON at render time. Switch document types to see how the same API shape drives different outputs.
Invoice
Statement
Certificate
Report
Built visually, controlled precisely
A real Studio — framed, not reskinned
Designers and operators edit templates in the visual Studio. Marketing shows the product as it is; the canvas, toolbars, and panels stay unchanged inside the app.
Dynamic expressions
Tables and charts
AI assistant
Publish version
Render from any stack
Copy a real request. Get a PDF back.
Snippets call https://api.makepdf.co.uk/api/pdf/render-template, the same endpoint documented in the portal. The template ID stays stable, and production can pin a published version so layout changes do not move live renders.
Response
200 OK
application/pdf
Latency842 ms
Size186 kB
Request IDreq_8f2a…c91
AI and MCP
Edit with the assistant, or from your editor.
Studio chat and the MCP server run the same template operations on the drafts you publish.
AI assistant in Studio
Ask for layout and content edits, upload Word, HTML, or PDF, and undo, save, or publish from the chat.
Checked before you publish
The assistant validates structure and renders a real preview, including warnings you can fix in the same draft.
MCP server
Connect Cursor or Claude Desktop to one HTTP endpoint with your workspace API key.
Same templates, scoped to you
MCP reads and edits only that workspace: create, validate, preview, and publish the drafts you see in the portal.