API changelog
All versions of the eRechio API (https://api.erechio.de), newest first. The current version is in the version field of GET /v1/status.
Versioning and deprecation
- The version number has the form
MAJOR.MINOR.PATCH. The current one is in theversionfield ofGET /v1/status. - Within
/v1only backward-compatible changes are made: new optional fields, headers and endpoints (MINOR) and bug fixes (PATCH). Clients must ignore unknown fields. - Incompatible changes are made only under a new path (
/v2). - We announce the deprecation of
/v1or of a field at least 3 months in advance on this page and on the status page; customers with Starter access additionally by e-mail. - Deprecated fields are kept in
/v1. Currently deprecated:valid(equal tovollstaendig_validiert). - Changes to the validation rules (KoSIT configuration, rule version) are listed separately on rule version and changes.
Versions
- Version 1.5.0 (22 Nov 2026): MCP: tool names in English and consistent:
validate_invoice(formerlyrechnung_pruefen) andget_status(formerlystatus); the old names are still accepted until at least 22 Feb 2027 but no longer shown intools/list. New toolexplain_rule: explains a rule code (e.g.BR-DE-15) in German, no key needed, not counted. Complete tool and parameter descriptions (result, errors, limits); name and descriptions in the directories in English. Results and messages stay German;/v1unchanged. - Version 1.4.1 (22 Nov 2026): Bug fix: the warning
BR-DE-19orBR-DE-20(“shall contain a correct IBAN”) also appeared for correct IBANs, because the rule engine computed the check digits (mod 97) imprecisely for long numbers. The IBAN is now recalculated exactly with the same formula as in the KoSIT rules; the warning remains only for a wrong IBAN. Same rule set, no change to fields or response codes. Also applies to the validator in the browser. - Version 1.4.0 (22 Nov 2026): MCP endpoint
https://api.erechio.de/mcp(Model Context Protocol, Streamable HTTP) with the toolsrechnung_pruefenandstatus; same API key, same quota, documentation: MCP connection. Optional headerIdempotency-KeyforPOST /v1/validate: a repeat with the same key and the same content within 24 hours returns the stored result with the headerIdempotent-Replayed: trueand is not counted again against the quota; different content with the same key: 422idempotenz_konflikt; a request with the same key still running: 409idempotenz_laeuft. New:/.well-known/api-catalog(RFC 9727). Backward compatible, nothing is removed. - Version 1.3.0 (23 Oct 2026):
/v1/statusreports the real state:okonly with a ready validation process, readable keys and writable usage data, otherwisegestörtwith HTTP 503 andgruende; in that state validations are rejected with 503gestoert(before, the status always saidok). Counting happens only after the response has been sent completely; errors while saving the counter do not change the response. If the client closes the connection, the validation is stopped, even while queued. Queued validations behind expired ones start immediately (before, a free validation process could stay idle). - Version 1.2.0 (22 Oct 2026): New field
regelstandin the result and in/v1/status: identifier of the rule and schema files used (start of their SHA-256). Sources, checksums and update test: rule version and changes. - Version 1.1.0 (21 Oct 2026): XSD schema check added. New fields
vollstaendig_validiert,regelpruefung_bestandenandschemapruefung.validis deprecated and now equalsvollstaendig_validiert(in 1.0.0 it was alreadytruewhen only the rule check passed). New message codesXSDandABBRUCH. Quota is reserved before the validation and counted only on 200; new status 503 withzeitlimitorausgelastet. - Version 1.0.0 (9 Oct 2026): First version, Schematron rules of the KoSIT configuration XRechnung 3.0.2.
To the API documentation · Status and support