What changed in the Invoice.xhub API — new countries and formats, new endpoints, and changes that affect the requests you send or the data you get back.
An RSS feed of this page is available at /changelog.rss — subscribe to hear about changes
before they reach your integration.
Typed request schemas on every parse endpoint
If you generate a client from our OpenAPI specification, it now knows what to send.
Previously, the 65 country- and format-specific parse endpoints carried no usable request schema. A
generated SDK turned that into an untyped, optional parameter — the required data field disappeared,
and calling the method with no arguments compiled cleanly. Only the server rejected it.
New endpoints
POST /api/v1/invoice/{countryCode}/{format}/embed— embed a generated e-invoice XML into your own carrier PDFGET /api/v1/verifactu/declaracionandGET /api/v1/verifactu/chain/{vatId}/export— Spanish VeriFactu declaration and chain export
Developer portal
The API reference now lives here, generated straight from the OpenAPI specification — so what you read is what the API actually accepts and returns, across all 86 endpoints and 37 countries.
What you get:
- Searchable reference for every endpoint, with request and response schemas
- Real examples on the parse endpoints — round-trippable documents you can send as-is
- Try it directly from the page, with your own API key
- Quickstart that reads a German XRechnung end to end