Electronic Invoice API
API by electronic-invoice.app · rest
Stage 1 and stage A of the API at api.electronic-invoice.app. Stateless: invoice content is processed in memory and is never stored or logged. Rule sets: KoSIT validator 1.6.3 with the XRechnung 3.0.2 configuration (release 2026-08-31, CEN EN 16931 Schematron 1.3.16), Mustangproject 2.26.0 for PDF/A-3 and generation, KoSIT xrechnung-visualization v2026-10-13 for HTML and for the business term model. Endpoints: validate (plus opt-in checks=plausibility), validate/batch, generate (invoice, credit note, corrective, partial and final invoice, optional payment QR), visualize, convert, extract (JSON, CSV, DATEV). Authentication at the gateway: Authorization: Bearer eia_live_.... What counts against the quota. Answers of the service with status 200, 400, 422 and also 504 count as one call. 401, 403, 404, 405, 411, 413, 429, 500, 502, 503 and /v1/health do not count. validate/batch counts one call per validated invoice file (response header X-Billable-Units).…
Endpoint: https://api.electronic-invoice.app/
Verification: observed. Source: crawl.
Capabilities (7)
- Convert UBL to CII CII to UBL or XML to ZUGFeRD / Factur-X PDF
- Extract invoice data as JSON CSV or a DATEV Buchungsstapel
- Generate an e-invoice from JSON
- Liveness and rule set versions
- Validate an e-invoice (XML or PDF)
- Validate many invoices from a ZIP archive
- Render an XML invoice or ZUGFeRD PDF as readable HTML or PDF