E-invoice compliantvia REST API.
XRechnung and ZUGFeRD via API — KoSIT-validated, EN 16931 compliant, processed in the EU. Peppol from 2027.
Got an ERP or a shop? We check one of your invoices for free, the written verdict arrives within one business day — and the integration that follows runs at a fixed price of 6,000–15,000 € plus VAT in 4–6 weeks.
- 37
- Countries
- 14
- Formats
Who this is built for
Three groups, one click to your case: what comes in, what the API makes of it — and what it explicitly does not do.
Businesses that issue invoices
The invoice is written in Word, Excel or the shop, and from 2027/2028 the buyer asks for XML.
Businesses that receive invoices
Invoices arrive as PDF, as XML or as both, and bookkeeping wants figures, not files.
Software vendors and agencies
The ERP is finished, only the e-invoice is missing, and the client is asking next week.
Quickstart
E-Invoices in 3 Steps
No complex XML logic, no manual validation. Automation in just a few lines of code.
- 01
Get API Key
Create your account in seconds and instantly receive your free API key for development.
- 02
Integrate SDK
Use our typed SDKs for Node.js, Python, or Go, or call the REST API directly.
- 03
Hand the e-invoice on
Generate valid XRechnung & ZUGFeRD PDFs and hand them to your delivery channel — email, portal or access point. The API does not send them itself.
# 1. Create account & copy API keyexport XHUB_API_KEY="sk_live_..."# 2. Build your first request — invoice.json{ "invoice": { "invoiceNumber": "RE-2025-001", "type": "invoice", "issueDate": "2025-01-15", "dueDate": "2025-02-15", "currency": "EUR", "seller": {"name":"Muster GmbH","vatId":"DE811128135","street":"Musterstraße 1","postalCode":"10115","city":"Berlin","countryCode":"DE","email":"info@muster.de","phone":"+49 30 12345678","bankAccount":{"iban":"DE89370400440532013000","bic":"COBADEFFXXX"}}, "buyer": {"name":"Beispiel AG","vatId":"DE136695976","street":"Beispielweg 42","postalCode":"80331","city":"München","countryCode":"DE"}, "items": [{"position":1,"description":"Beratungsleistung","quantity":10,"unit":"HUR","unitPrice":150,"taxRate":19,"netAmount":1500,"taxAmount":285,"grossAmount":1785}], "taxSummary": [{"taxRate":19,"netAmount":1500,"taxAmount":285}], "subtotal": 1500, "total": 1785, "paymentTerms": {"dueDays":30,"description":"Zahlbar innerhalb von 30 Tagen"}, "countrySpecific": {"countryCode":"DE","leitwegId":"991-12345-67"} }} curl -X POST https://service.invoice-api.xhub.io/api/v1/invoice/de/zugferd/generate \ -H "Authorization: Bearer $XHUB_API_KEY" \ -H "Content-Type: application/json" \ -d @invoice.json# 3. Response → PDF/A-3 with embedded EN-16931 XML# Content-Type: application/pdf# Ready to email or send via PeppolQuickstart
E-Invoices in 3 Steps
No complex XML logic, no manual validation. Automation in just a few lines of code.
Get API Key
Create your account in seconds and instantly receive your free API key for development.
# 1. Create account & copy API keyexport XHUB_API_KEY="sk_live_..."Integrate SDK
Use our typed SDKs for Node.js, Python, or Go, or call the REST API directly.
# 2. Build your first request — invoice.json{ "invoice": { "invoiceNumber": "RE-2025-001", "type": "invoice", "issueDate": "2025-01-15", "dueDate": "2025-02-15", "currency": "EUR", "seller": {"name":"Muster GmbH","vatId":"DE811128135","street":"Musterstraße 1","postalCode":"10115","city":"Berlin","countryCode":"DE","email":"info@muster.de","phone":"+49 30 12345678","bankAccount":{"iban":"DE89370400440532013000","bic":"COBADEFFXXX"}}, "buyer": {"name":"Beispiel AG","vatId":"DE136695976","street":"Beispielweg 42","postalCode":"80331","city":"München","countryCode":"DE"}, "items": [{"position":1,"description":"Beratungsleistung","quantity":10,"unit":"HUR","unitPrice":150,"taxRate":19,"netAmount":1500,"taxAmount":285,"grossAmount":1785}], "taxSummary": [{"taxRate":19,"netAmount":1500,"taxAmount":285}], "subtotal": 1500, "total": 1785, "paymentTerms": {"dueDays":30,"description":"Zahlbar innerhalb von 30 Tagen"}, "countrySpecific": {"countryCode":"DE","leitwegId":"991-12345-67"} }} curl -X POST https://service.invoice-api.xhub.io/api/v1/invoice/de/zugferd/generate \ -H "Authorization: Bearer $XHUB_API_KEY" \ -H "Content-Type: application/json" \ -d @invoice.jsonHand the e-invoice on
Generate valid XRechnung & ZUGFeRD PDFs and hand them to your delivery channel — email, portal or access point. The API does not send them itself.
# 3. Response → PDF/A-3 with embedded EN-16931 XML# Content-Type: application/pdf# Ready to email or send via PeppolFeatures
Built for German Compliance
All important standards in one API.
Developer-First
REST + JSON instead of SOAP/XML. No templates, no dependencies.
GoBD Compliant
Format fidelity, traceability and KoSIT validation as the basis. Audit-proof archiving follows with the Archive API (planned 2027).
PDF attachments
Embed arbitrary files as PDF/A-3 compliant attachments in ZUGFeRD or Factur-X invoices — proofs of service, audit reports, T&Cs.
Automation-Ready
Integrated with Zapier, Make.com, and n8n for no-code workflows.
Team & roles
Multiple users per organization, roles with fine-grained permissions, email invitations — directly from the Console.
Peppol Gateway
Send e-invoices directly via the Peppol network. Planned 2027 — not available yet.
Developer-First API
The Stripe of E-Invoicing APIs
While other e-invoicing solutions rely on UI platforms or complex SOAP/XML interfaces, we offer a modern REST API that developers love.
5 Minutes
to your first e-invoice
1 Endpoint
for all 14 formats
0 Dependencies
just HTTP + JSON
APIs
6 APIs. 37 Countries. One Ecosystem.
Each API usable standalone. Perfectly combinable. Country-specific formats.
Invoice Generator APIMost Popular API
Generate PDF, XRechnung & ZUGFeRD for 37 countries
POST /api/v1/invoice/{countryCode}/{format}/generateParser API
Extract structured data from e-invoices
POST /api/v1/invoice/parseValidator API
Validation against the target country's rule set (DE: KoSIT Schematron)
POST /api/v1/invoice/{countryCode}/validateFormats API
Retrieve all supported formats and countries
GET /api/v1/invoice/formatsConverter API
Convert between XRechnung, ZUGFeRD and Factur-X
POST /api/v1/invoice/convertAttachments API
Embed files into an existing invoice PDF
POST /api/v1/invoice/attachmentsTransparent Pricing
No hidden costs. Pay only for what you use.
| Feature | Free | Starter | Premium | Enterprise |
|---|---|---|---|---|
| Price / month | 0 € | 23 € | 79 € | on request |
| billed annually | 0 € | 18 € | 62 € | — |
| API calls / month | 20 | 2,000 | 7,500 | volume pricing |
| Line items per invoice | 25 | 100 | 1,000 | individual |
| Rate limit | 5/min | 50/min | 200/min | custom |
| SLA | — | 99.5 % | 99.9 % | 99.99 %+ |
| Support | Community | Email 48 h | Priority 8 h | Account manager |
| Additional calls | — | €0.02 each | €0.01 each | by contract |
All prices net, plus VAT · 20 % off when billed annually · Free tier without a credit card
What happens above the limit
On a paid plan nothing is switched off: calls above your included volume are billed per call at the rate in the table, and you get an email at 80 % and at 100 % of your quota — so an upgrade is a decision and never a surprise. On the free tier calls are rejected at the limit (429) rather than billed.
Line items behave differently: an invoice with more line items than the plan allows (15,000 at the absolute most) is rejected with HTTP 400 — nothing is produced and nothing is billed.
For comparison: classic e-invoicing software bills per user per month. The API bills per invoice — for automated processes that is the cheaper route. See the comparisons
Wondering what happens to your invoicing if we are no longer around? We answer that here
Before you roll it out
The three questions your DPO will ask
Invoice data is personal and tax-relevant. Rollouts fail at approval, not at the integration — so these are answered up front.
Where it runs
Processing happens in EU regions. Our hosting provider (Vercel Inc.) is US-incorporated and acts as a processor under a DPA with EU data residency — we name it rather than claim a purely German stack.
What we keep
Invoice data is taken in for processing, the result is returned. What is retained, for how long and why is set out on the security page — including request logs and the planned Archive API, where storage is the point.
Contracts and proof
The subprocessor list and the technical measures are on the security page — open, no form. The data processing agreement under Art. 28 GDPR we send on request by email; it does not exist as a download yet, and we say so rather than implying it does.
Invoice-api.xhub Blog
Insights, tutorials, and news about e-invoicing, API development, and the German compliance landscape.
Your Own Fields on an E-Invoice — Without Losing Conformance
Vessel name, job number, machine serial: data EN 16931 doesn't know but your customer needs. Why a hybrid e-invoice has two layers — and where the boundary actually runs.
From PDF Invoice to E-Invoice: What Our First Customer Pipeline Taught Us
A facility services company writes its invoices in Word and Excel and must send e-invoices from 2027. How we built a pipeline behind that with n8n and the invoice-api — without a language model, with seven mapping errors that only the real API call revealed, and three findings in our own API.
E-Invoicing Mandate 2025: n8n Automation for Small Businesses
Germany's e-invoicing mandate affects every business. How SMBs automate invoice creation for free with n8n and the xhub.io API — incl. ROI numbers.
FAQ
Frequently Asked Questions
Everything you need to know about Invoice-api.xhub.
More questions? Contact us