Ist Invoice-api.xhub GoBD-konform?

Invoice-api.xhub unterstützt Sie bei der Einhaltung der GoBD-Vorgaben: Die erzeugten XRechnung- und ZUGFeRD-Dateien sind formattreu nach EN 16931 und werden gegen die offiziellen KoSIT-Schematron-Regeln geprüft, was Nachvollziehbarkeit und maschinelle Auswertbarkeit sicherstellt. Die revisionssichere Langzeitarchivierung selbst bleibt bis zum Release der Archive API (geplant Q1/2027) in Ihrer Verantwortung.

Was passiert, wenn ich das Rate Limit überschreite?

Im Free-Tier werden Anfragen bei Überschreitung abgelehnt (429 Too Many Requests). In den kostenpflichtigen Tiers (Starter & Premium) können wir kurzzeitige Spitzen tolerieren oder bieten Upgrades an. Für Enterprise-Kunden gibt es Custom Rate Limits.

Kann ich die API auch lokal testen?

Absolut! Unsere API ist von überall erreichbar. Da es sich um eine reine REST-API handelt, gibt es keine lokalen Abhängigkeiten. Nutzen Sie einfach unseren Playground oder curl/Postman zum Testen.

Unterstützt ihr Peppol?

Noch nicht als Versand. Peppol-BIS-3.0-UBL können Sie heute schon erzeugen und validieren — der Peppol-Versand über unser Gateway ist für Q1/2027 geplant. Den Stand aller Endpoints finden Sie auf der Roadmap; dort können Sie sich für Peppol benachrichtigen lassen.

Wie wird abgerechnet?

Wir rechnen monatlich oder jährlich per Kreditkarte (Stripe) ab. Unternehmen auf dem Business/Enterprise Plan können auch per Rechnung zahlen.

Ihr seid ein kleines Team — was passiert mit meiner Rechnungsstellung, wenn es euch nicht mehr gibt?

Berechtigte Frage, und wir beantworten sie offen. XRechnung, ZUGFeRD und Peppol BIS 3.0 sind öffentliche Normen nach EN 16931 — jede Rechnung, die unsere API erzeugt, bleibt auch ohne uns gültig und ist von jedem anderen Anbieter verarbeitbar. Die API ist REST hinter einem Adapter in Ihrem System; ein Anbieterwechsel betrifft diesen Adapter, nicht Ihre Rechnungsstellung. Details dazu stehen auf der Sicherheitsseite unter „Fortbestand“.

NewConsole update: new dashboard & live API playground

E-invoice compliantvia REST API.

XRechnung and ZUGFeRD via API — KoSIT-validated, EN 16931 compliant, processed in the EU. Peppol from Q1/2027.

or try it in the Playground

Existing ERP or shop? We handle the integration — fixed price, fixed timeframe. Checking one of your invoices is free.

28
Countries: 11
Formats: 200ms
Avg. Latency: 99.9%
Uptime target

Integrated with your tools

n8n

n8n

View all integrations

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
Send E-Invoice
Generate valid XRechnung & ZUGFeRD PDFs and automatically send them to your customers.

bash

# 1. Create account & copy API key
export XHUB_API_KEY="xhub_sk_..."

bash

# 2. Build your first request
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

bash

# 3. Response → PDF/A-3 with embedded EN-16931 XML
# Content-Type: application/pdf
# Ready to email or send via Peppol

Go to Quickstart Guide

Quickstart

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.

bash

# 1. Create account & copy API key
export XHUB_API_KEY="xhub_sk_..."

Integrate SDK

Use our typed SDKs for Node.js, Python, or Go, or call the REST API directly.

bash

# 2. Build your first request
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

Send E-Invoice

Generate valid XRechnung & ZUGFeRD PDFs and automatically send them to your customers.

bash

# 3. Response → PDF/A-3 with embedded EN-16931 XML
# Content-Type: application/pdf
# Ready to email or send via Peppol

Go to Quickstart Guide

EXPLAINED IN 60 SECONDS

Watch JSON become a compliant e-invoice

One API call, one PDF/A-3 with embedded EN-16931 XML. XRechnung, ZUGFeRD, Peppol — KoSIT-validated, GDPR-compliant, hosted in the EU.

API key in 60 seconds

Free to start, no credit card required. Production-ready from day one.

Features

Built for German Compliance

All important certifications and standards in one API.

KoSIT Validated

Official Schematron validation against current KoSIT schemas.

28 Countries

DE, AT, CH, FR, IT, ES, NL, BE, PT, PL, CZ, HU, RO, BG, SE, NO, DK, FI, IE, GB, LU, MT, CY, SI, EE, LV, LT, GR — one API call.

12 Formats

XRechnung 3.0.2, ZUGFeRD 2.4, Factur-X 1.08, FatturaPA, Peppol BIS 3.0 UBL, ebInterface, qr-bill, and more.

~200ms Response

Fast API responses for seamless integration into real-time workflows.

Peppol Gateway

Send e-invoices directly via the Peppol network. Planned Q1/2027 — not available yet.

GoBD Compliant

Format fidelity, traceability and KoSIT validation as the basis. Audit-proof archiving follows with the Archive API (planned Q1/2027).

Developer-First

REST + JSON instead of SOAP/XML. No templates, no dependencies.

Enterprise-Ready

99.9% SLA, dedicated support, and on-premise option available.

PDF attachments

Embed arbitrary files as PDF/A-3 compliant attachments in ZUGFeRD or Factur-X invoices — proofs of service, audit reports, T&Cs.

Team & roles

Multiple users per organization, roles with fine-grained permissions, email invitations — directly from the Console.

Automation-Ready

Integrated with Zapier, Make.com, and n8n for no-code workflows.

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 11 formats

0 Dependencies

just HTTP + JSON

APIs

4 APIs. 28 Countries. One Ecosystem.

Each API usable standalone. Perfectly combinable. Country-specific formats.

Invoice Generator APIMost Popular API

Generate PDF, XRechnung & ZUGFeRD for 14 countries

POST /api/v1/invoice/{countryCode}/{format}/generate

Parser API

Extract structured data from e-invoices

POST /api/v1/invoice/parse

Validator API

Country-specific validation - free without quota

POST /api/v1/invoice/{countryCode}/validate

Formats API

Retrieve all supported formats and countries

GET /api/v1/invoice/formats

View all APIs

Transparent Pricing

No hidden costs. Pay only for what you use.

Plans and prices
Feature	Free	Starter	Premium	Enterprise
Price / month	0 €	23 €	79 €	on request
billed annually	0 €	18 €	62 €	—
API calls / month	20	2,000	20,000	volume pricing
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.

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

Get an API key — free All plans and features

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

A data processing agreement under Art. 28 GDPR, the list of subprocessors and the technical measures belong in the hands of your DPO before anyone talks to us — not behind a form.

Security, subprocessors and data processing agreement

THE FULL TOUR