Developers
OpenAPI ↗
Go to the app
Documentation / API v1
API v1 · API v1

Documents

XRechnung and ZUGFeRD generate, parse, validate and download.

On this page

Document end points

All paths are relative to /api/v1/sandbox or /api/v1/liveThe complete JSON schemes are in the OpenAPI specification.

EndpointInput/FunctionLegal basis
POST/documents/generateJSON → validated XRechnung UBL or ZUGFeRD PDF.Generate
POST/documents/parseOriginal XML or ZUGFeRD PDF → structured data.Process
POST/documents/validateOriginal technical check and report received.Process
GET/documents/{id}Data, findings, checksums and artifact URLs.Read

Entries and supported profiles

Send XML/PDF as an unchanged request body, without multipart packaging: application/xml or application/pdfGeneration used application/jsonEvery processing POST requires a stable Idempotency-Key.

  • Generation: EUR, 0 / 7 / 19% sales tax, maximum 100 items with positive quantities. quantity and individual price up to 1,000,000, each maximum of four decimal places.
  • At 0 %, the control keys and the necessary grounds for exemption must be provided; profile-dependent mandatory information must be provided.
  • Credits/cancellations: documentType: credit_note, sourceNumber and sourceDateThe reference is provided by the caller and does not link an app booking.
  • Parsing reads UBL Invoice/CreditNote and CII without inventing missing amounts as zero.

Correct classification of technical results

XRechnung is checked with KoSIT. ZUGFeRD-EN16931 PDFs are checked with Mustang including PDF/A. A stand-alone generic CII file is not a ZUGFeRD PDF.

validationStatusSignificance
ValidThe specified technical rules were passed.
InvalidExamination completed, errors found. Original and report remain.
Not_checkedParsing only. No statement of conformity.

Answers contain a set of rules and the time of testing. Technical tests prove neither tax correctness nor conformity of visible PDF content and embedded XML.

Download originals and reports

GET /documents/{id}/…Artificial artefact
OriginalUnchanged original uploaded or generated file.
xmlStructured XML, if any.
pdfPDF view of a validly generated XRechnung, if available.
ReportOriginal validation report, if available.

Non-existent artifacts deliver 404. X-Content-SHA256; the metadata contains file size, type and hash. The SDK verifies the checksum.

Re-processing does not replace historical originals or reports; automatic deletion is not enabled; operators schedule backups and memory monitoring.

The connection is restored...

New connection attempt in seconds.

The connection could not be restored.
Please try again or reload the page.

Your meeting was paused.

The sitting could not be continued.
Please try again or reload the page.