Changelog
What changed, and when
API changes are additive within a major version. Deprecations are announced here at least 12 months ahead.
A ten-minute product tour
- docs
The dashboard now offers a ten-minute tour of the whole path from a template to the first API call: the visual editor and HTML, fields, repeats and conditions, sample data and the JSON schema, publishing and versions, API keys, a request from Postman, renders, delivery and batches.
- Where: at the end of the onboarding and next to the "Get to your first render" checklist on the home page.
- Which version: whoever plans to generate invoices sees the invoice example, everyone else the certificate example.
- Privacy: the video loads from YouTube only when you click play.
E-invoice checks read the invoice data
- api
A check with
POST /v1/einvoices/validatenow answers with what the invoice states, next to the verdict:invoice: supplier and buyer, number, type, dates, payment terms, bank details and lines, with the field names of the invoice you send toPOST /v1/einvoices.vat_breakdownandtotals: the amounts as the invoice states them.- Every verdict: valid and invalid invoices both carry the data, so a reply to the supplier can name the invoice. It costs nothing extra.
An inbound pipeline can now register, book and pay a ZUGFeRD PDF or an XRechnung XML without parsing CII or UBL itself. The MCP tool
validate_einvoicereturns the data too, and the n8n node has a new operation, E-Invoice → Validate (0.1.2).See What the invoice states for the fields and the limits.
Validate the e-invoices you receive
- api
POST /v1/einvoices/validatechecks an e-invoice you received, from any sender, with the same validators and rules as the e-invoices Dynamic Document API generates:- Hybrid PDFs: Factur-X and ZUGFeRD 2.x, and PDFs carrying an
xrechnung.xml. The embedded XML is checked with the KoSIT validator, and the PDF as received with veraPDF against PDF/A-3b. - XML: XRechnung 3.0, EN 16931 and the Factur-X / ZUGFeRD profiles, in UN/CEFACT CII or UBL 2.1.
- The verdict is
result.valid, with the detected profile and syntax and the validators' reports, rule by rule.
A check with a verdict, valid or invalid, is 1 billed render, and checks are available on every plan, Free included. A file that isn't an e-invoice answers
422 einvoice_not_foundand costs nothing. The MCP server has a matchingvalidate_einvoicetool.See Validate e-invoices for the sources, the supported formats and the limits.
Dynamic Document API on Integrately
- integrations
Integrately has released a Dynamic Document API integration, built and maintained by Integrately.
- Triggers: a template version is published, a render succeeds or fails, a batch is completed.
- Actions: create PDFs from templates, HTML, URLs and Markdown, images from templates, e-invoices and batches; merge and protect PDFs; upload files; sign image URLs; wait for a render, delete its files, and look up templates, renders, batches and account usage.
All SDKs and platform integrations are listed in SDKs and integrations.
Free plan now includes 50 renders a month
- pricing
The Free plan now includes 50 renders per month instead of 10. Existing Free workspaces get the new allowance with their next cycle; the plans and limits page has the updated table.
Nothing else changes: Free keeps 2 templates, 1 member and 7 days of file retention, has no auto top-ups, and can buy render packs when 50 renders are not enough.
Billing in renders, new Free plan and payments through Link
- pricing
- api
Usage is now counted in renders instead of credits, and every weight is a whole number.
- A PDF of up to 50 pages is 1 render, plus 1 for each additional 50 pages. An image is 1 render per output size. PDF tools, PDF/A conversion and e-invoice XML exports are 1 render each. The e-invoice layer on a PDF render is now included at no extra cost. See what counts as a render.
- The Free plan includes 10 renders per month and up to 2 templates. Paid plans keep their prices and include 3,000 (Starter), 15,000 (Growth), 50,000 (Pro) and 200,000 (Scale) renders.
- Metered overage is replaced by auto top-up. When fewer than 200 renders are left, we add 1,000 renders at the plan's top-up price (€6 Starter, €4 Growth, €3 Pro, €2 Scale, excluding VAT), and Stripe (via Link) charges the card within about 24 hours. Unused renders roll over and expire after 12 months, oldest first. A new top-up is only added after the previous one is paid. The spend cap is now the monthly top-up limit (default twice the plan price,
0turns auto top-ups off); when no top-up can be added, live renders stop with402 render_limit_reached. The API calls auto top-upsrender_blocks. See auto top-up. - Render packs of 10,000, 50,000 and 250,000 renders, valid for 12 months, are now for the Free plan only. Packs bought on Free stay usable after upgrading.
- Prices are now in euros only, with the same numerals as before: €19, €59, €149 and €399 per month (20 % less when billed annually), auto top-ups from €2 and render packs from €50. All prices exclude VAT, which Stripe adds at checkout based on your location. There is no currency choice any more.
- Payments are processed by Stripe with Link as the seller of record: receipts and invoices come from Link, card statements show
LINK.COM*, and Stripe calculates the tax. Enter your tax ID at checkout.
Breaking API changes:
- The render object's
creditsfield is nowbilled_renders, an integer. The same applies to render webhooks and the points ofGET /v1/usage. - The binary-delivery header
X-Creditsis nowX-Billed-Renders. - The
402error codecredits_exhaustedis nowrender_limit_reached, also as thepaused.reasonof batches. GET /v1/accountreturnsrendersinstead ofcredits, and theusage.threshold_reachedwebhook event carriesrendersinstead ofcredits. All values are integers. Therendersobject is{included, used, remaining_included, prepaid_remaining, spend_cap_cents}:overage_usedis gone andtopup_remainingis nowprepaid_remaining(render packs plus auto top-ups).- The TypeScript SDK raises
RenderLimitReachedError(a subclass ofBillingError) forrender_limit_reached, and binary renders exposebilledRendersinstead ofcredits.
Documentation and API reference
- docs
- api
The documentation is now public.
- Guides for renders, PDF and image options, headers and footers, pagination and webhooks, each with cURL, TypeScript and Python examples.
- Template language reference covering the Jinja syntax and every document filter, from
format_currencytoqrcodeandbarcode. - API reference generated from the OpenAPI 3.1 description of the renders, uploads and account endpoints.
- Markdown for tools and language models: append
/index.mdto any documentation URL, or start from/llms.txt.
Template gallery with 30 starter templates
- templates
The template gallery launches with 30 original starter templates across 15 categories.
Every template page shows the variables the template expects, realistic sample data and the complete source: body markup, stylesheet and header and footer settings. Use this template opens a free workspace with the template preloaded, ready to edit and publish as your own version.
Templates are plain HTML, CSS and Jinja, so they work with the same filters documented in the template language reference.
Free PDF tools that run in your browser
- tools
Eight free tools for everyday PDF tasks are available at /tools:
- Merge, split, rotate and extract pages
- Edit document metadata
- Add text watermarks and page numbers
- Convert pages to PNG or JPEG
All processing happens locally with open-source libraries; documents are never sent to a server. The same operations are part of the PDF tools API, starting with merge.
Published pricing and cost calculator
- pricing
Pricing is now public, including the complete credit table.
- One credit per PDF of up to 50 pages and one per image.
- Paid plans continue past their included credits at a published overage rate, limited by a spend cap that defaults to twice the plan price.
- The calculator takes your monthly volume and requirements, recommends the cheapest plan that fits and compares monthly with annual billing.