PDF Generator API

White-label document template editor you embed in your SaaS or ERP

Your customers edit their own invoice, order and report templates inside your product. One API call returns a URL you load in an iframe, scoped to that customer's workspace, so per-customer templates stay isolated in a multi-tenant setup. Your developers stop being the template team.

Test, build, and integrate. Start your 14-day FREE trial. No credit card required!

Create template, generate document, review & sign using single API.
1,500+
companies trust us

6M+
documents generated monthly

Information security

Trusted by teams featured in our case studies

One API for everything

Design, Generate, Deliver

One developer platform covers the whole path, from your customer opening the editor to a finished document leaving your application. You build against one API and one set of credentials. We run the editor, the rendering, the storage and the audit trail on infrastructure that is ISO 27001 certified and GDPR compliant.

  • AI Template Builder: Describe or upload your existing PDF or DOCX

  • Drag-and-drop editor your non-technical users can actually operate

  • Page breaks, headers and footers, dynamic tables, conditional formatting

  • Barcodes, QR codes, charts and images as first-class components

  • Expression language for calculations and data-driven logic

  • The same template renders through the generation API at any volume

Most template editors are built for your team. This one is built for your users.

Template editors usually sit in an admin panel that only your team can reach. A customer wants their delivery note changed, so they email support, support writes a ticket, a developer edits a layout file, and the change ships with the next release. The customer waited two weeks for a moved logo.

PDF Generator API inverts that. Design the starting templates once, then open the editor inside your product and let each customer adjust their own copy. Call POST /templates/{templateId}/editor and you get back a unique URL that already carries the authentication. Drop it into an iframe, or redirect the user to it. They edit, they save, and the next document your application generates uses their version.

See how it works in the live editor
Manual changes by admin or developer in code

Stop building a template editor. It is a bigger product than you think.

A document editor looks like a week of work until you start. You need a canvas that maps to physical page sizes, page break behaviour that survives a table of unknown length, headers and footers that repeat, a data field picker, a preview that matches the printed output, and a renderer that produces the same result on every browser your customers use.

Then it never stays finished. Someone needs a second page. Someone needs a barcode. Someone needs the tax row hidden when the buyer is outside the EU. Someone needs the whole thing in German. Every one of those is a ticket against the editor you built to reduce tickets, and none of it is the product your users signed up for.

PDF Generator API gives you the editor as an API. We maintain the canvas, the components, the renderer and the browser support. You get a URL, embed it, and ship.

Read: building versus buying a document generation solution
Embedded document editor

Ready to take control?

Simple Packing Slip

Platforms that already embedded it

The editor is why they chose us

SaaS and ERP vendors embed the template editor so their own customers can change an invoice, packing slip or order document without a support ticket. Here is what that changed for them.

All case studies →

United Kingdom
★★★★★

The reason we chose PDF Generator was the template editor. Building our own would have wasted our development time.

5+ years in production · customers build their own templates

Calum McClune

Calum McClune
Technical Team Lead · Veeqo

Read the story →

Canada
★★★★★

It probably saves us around six hours of support time per onboarding.

Default templates customers copy and edit · integration untouched for years

Rob Tigwell

Rob Tigwell
CTO · OrderEase

Read the story →

South Africa
★★★★★

It would be really hard without this for us to build actual PDF documents for clients.

213 templates across their client base · one integration

Stubber

Luke Steffens
Solutions Architect · Stubber

Read the story →

Coming off Crystal Reports, SSRS or hardcoded templates

Most platforms arrive here from a desktop report designer like Crystal Reports, SSRS or Jasper, or from templates hardcoded in the codebase. Both tie the layout to your release cycle, and neither can be handed to a customer. There is no report-file import, but there is a path: load a printed PDF of the report as the template background, map your JSON fields onto it, publish it as an organization default so every existing tenant keeps today’s layout, then open the editor for the customers who want their own variant. Paragon ERP was charging thousands per template change before they moved.

Send us a report you want to move and we will build the template with you.
partner-white-label-square

What it costs you, and how platforms charge for it

You pay for document volume, not for tenants. Workspaces are unlimited from the Professional plan up, so onboarding your four-hundredth customer costs the same as your fourth. Volume is counted in credits, one credit per five pages, so a two-page invoice and a five-page invoice cost the same. The embedded editor is available from the Basic plan.

Not sure which tier fits your tenant count? Send us your customer count and monthly document volume and we will size it.

What is an embedded template editor?

An embedded template editor is a document design interface that runs inside your product rather than inside ours. You call the Open Editor endpoint, get back a secure single-use URL, and load it in an iframe or as a redirect. Your customer arranges text, tables, images, barcodes and charts on a real page canvas, inserts data fields from their own data set, previews the result, and saves. The template belongs to that customer's workspace, so their changes affect their documents and nobody else's. When your application next calls the generation API, it renders their saved version. There is no editor UI to design, no rendering engine to maintain, and no separate account for your users to create.

Prototype your integration today with a 14-day FREE trial. No credit card required.

Talk to us before you build

Meet Michal Líška. He is our pre-sales engineer and knows our service inside out. He can answer any questions that you might have about implementing PDF Generator API or document automation in general.
Michal Liska

Questions

Before you embed it

How do I embed the editor?

Call POST /templates/{templateId}/editor and you get back a unique URL. Set it as the src of an iframe to render the editor inside your own layout, or use it as a redirect target. The URL already carries the authentication, so there are no extra parameters to append. For the iframe route, the browser has to allow third-party cookies.

Do my users need their own PDF Generator API account?

No. They work inside a workspace that belongs to your organization. Your backend signs the token that opens the editor, so there is no separate signup, no separate login, and no credentials of ours for your users to manage.

How do I keep one customer’s templates away from another’s?

Put each customer in their own workspace. A workspace has access to its own templates plus your organization default templates, and nothing else. The workspace identifier travels in the sub claim of the token you sign server-side, so the scoping is decided by your backend and never by the browser.

Can I give every new customer a starting set of templates?

Yes. Set a template’s access type to Organization under Page Setup and it becomes available to every workspace in your account. Your users find it in the New menu in the editor and copy it into their own workspace to adjust.

How do I authenticate?

Requests use a JSON Web Token as a Bearer token, signed server-side with your API key and secret. The mandatory claims are iss for your API key, sub for the workspace identifier, and exp for expiry, which should be short. The base URL for all endpoints is https://us1.pdfgeneratorapi.com/api/v4.

Can my users work in their own language?

Set language on the Open Editor request to en, et, cs, sk, ru or de. Leave it out and the editor follows your organization’s default editor language.

Can users bring a PDF they already have?

Yes. Import from PDF loads their existing file as the background of a new template with editable areas detected automatically, so they adjust a document they already use instead of rebuilding it from a blank page.

What else can I do once the template exists?

The same template and the same API cover document generation at volume, web forms, an embeddable review and sign flow, PDF/UA accessible output, e-invoicing, and PDF services like merging, watermarking and form filling.