For software & developers Your documents. Printed in your layout.
Two ways through the same API: brandbill keeps customers, number series and archive for you — or your system keeps everything and brandbill only prints. You design the template in the editor, the PDF comes back.
Print only: how the integration works
Three steps from your own system to the finished PDF.
-
01
Design a template
Create an invoice, quote or letterhead in the editor. GET /api/v1/templates lists every template with the placeholders it needs — and where each value comes from.
-
02
A “print only” key
Under Settings → API keys, create a key with the scope “print only”. It reaches printing and templates, nothing else.
-
03
Send documents
Number, date, customer, lines and your totals to POST /api/v1/render. If the totals differ, nothing is printed — your PDF never shows other amounts than you book.
curl -X POST https://brandbill.de/api/v1/render \
-H "Authorization: Bearer bb_…" \
-H "Content-Type: application/json" \
-d '{
"type": "invoice",
"number": "2026-00042",
"issue_date": "2026-10-26",
"customer_name": "Kunde GmbH",
"lines": [{ "description": "Leistung", "quantity": 1,
"unit_price": 1200, "vat_rate": 19 }],
"expected_totals": { "net_cents": 120000,
"vat_cents": 22800, "gross_cents": 142800 }
}' \
-o 2026-00042.pdf
We use it ourselves
Our own PSA — projects, time, bookkeeping — prints quotes, invoices, partial invoices and payment reminders exactly like this: it keeps the number series, payments and DATEV, brandbill provides the layout. A reminder is printed from the invoice template, with open amount, fee and interest.
- Quote, invoice, partial and final invoice, correction, cancellation, reminder, free text
- Repeated requests answered instantly from the cache until the template changes
- Preview without number and without counting
- Statistics count prints, never content
- The same number printed again counts once
In practice
Two systems. The same building block, plugged in to different depths.
Two integrations from our own work, without names: a retailer lets brandbill run all its paperwork, a project software keeps everything and only has brandbill print. Both use the same public API.
Your own system. Plug in the paperwork.
A retailer runs catalogue, shop, checkout and rentals in its own admin. Quotes, invoices with QR payment part, rental contracts, delivery notes and reminders come from brandbill — through the public API, with no custom code and no second login for the team.
- CHF and VAT
- QR-bill
- Total matched to the cent
- Key stays on the server
- Same API for every system
Everything stays in their own software. Only the layout comes from brandbill.
Projects, time, number sequence, payments and DATEV stay where they are. The software no longer has a PDF layout of its own: every quote, invoice, reminder and report goes to the print service and comes back in the template from the editor.
- No PDF layout of its own left in the software
- Number only after a successful print
- Totals, IBAN and VAT ID checked
- Printing stores nothing at brandbill
- E-invoice stays in its own system
From the system's point of view: three building blocks, alone or together
/api/v1 · REST & MCP
brandbill keeps the documents
Customers, quotes, invoices, payments, contracts. Number sequence, status and archive live in brandbill; your system just calls.
POST /api/v1/render
Your system leads, brandbill prints
You keep numbers and books, send document data with totals and get the PDF back in your template. Nothing is stored.
POST /api/v1/embed/session
The interface as a building block
brandbill screens right inside your application, with a short-lived token instead of a separate login. Your team stays in one tool.
What helps you
You choose where documents live
Create documents via the API and brandbill keeps number series, status and archive — just like in the app. Only print and no document, customer or number stays with us for good: original, archive and number series stay with you, we only count the prints.
Totals checked
You send your totals, brandbill recalculates. One cent off returns a clear error instead of a PDF — optionally for IBAN and VAT ID too.
Design without code
Layout, fonts, logo and fixed texts live in the editor, not in your code. A new template applies to every print at once, no deployment needed.
Included in every account
- Editor for layout, fonts and colours — on the free plan too
- E-invoicing as ZUGFeRD and XRechnung, incl. Leitweg-ID
- Quotes, invoices and reminders in the same look
- Payment code on the invoice: scan with your banking app, done
- ZIP export for your tax advisor
- Servers in Germany, no tracking cookies
01 What does brandbill store of my documents?
That depends on the way. Create documents (POST /api/v1/documents) and brandbill stores them like in the app — with number, status and archive. Print only (POST /api/v1/render) and nothing of the content: we count how many PDFs were delivered per day and key; so that printing the same number again does not count twice, only a check value (HMAC) remains — not the number itself. If the same request comes again right away, we answer it from an encrypted short-term cache that is deleted after 15 minutes.
02 Do prints count towards my plan’s quota?
Yes, final quotes and invoices count like documents created in the app. Previews, corrections, cancellations and reminders never count. The REST API is included from the Frühstück plan.
03 What about partial and final invoices?
Yes — they are invoices with their own number. Put the progress into the line (“progress 60 % (billed before 30 %)”), the title into subject (“2nd partial invoice — website”) and the reference to earlier invoices into intro_text. The final invoice deducts what was billed before as a negative line — brandbill checks the totals as for any invoice.
04 What about e-invoicing?
If brandbill keeps the documents, the e-invoice including its XML is created at brandbill. When only printing, the XML comes from your system, where the data lives: you embed it into the delivered PDF (ZUGFeRD), brandbill prints the layout for it.
05 What if printing fails?
The call answers 503 with a Retry-After. A template that cannot print never silently falls back to another layout — your archive stays consistent.
Your next invoice looks like you.
Create an account, upload your logo, get going. Free, no credit card.
brandbill is also for Self-employed · Freelancers · Designers · Architects · Photographers.