Skip to content

Changelog

This page documents all significant changes to the Invoicetronic API. Versions follow Semantic Versioning.

v1.0.25 - February 3, 2026

Fixes

  • The is_read field on received invoices (receive) is now set only when include_payload=true, both for single GET and list endpoints.
  • The Dashboard now allows creating and viewing webhooks without a company_id, to receive notifications from all companies on a single URL.
  • The Dashboard now properly handles webhook validation errors (e.g. invalid URL) by showing a user-friendly message instead of a server exception.

Documentation

  • Updated receive endpoint descriptions to document the new is_read behavior.
  • Fixed typos in model descriptions.

v1.0.24 - February 2, 2026

Fixes

  • Improved event logging.

v1.0.23 - February 2, 2026

Fixes

  • Fixed base64 decoding in Basic Auth authentication that could cause login failure when credentials were encoded without the colon separator (e.g. Base64(api_key) instead of Base64(api_key:)).

v1.0.22 - January 18, 2026

Improvements

Enhanced API documentation

Added comprehensive descriptions to all API endpoints with detailed information about: - Description of each entity (send, receive, update, company, log, webhook, status) - Data retention periods - Available filters for searches - Links to Dashboard for resource management - Links to Sandbox and Webhooks documentation

v1.0.21 - January 5, 2026

New Features

German language support

Added full support for German language (de) in the Accept-Language header. All error and validation messages are now available in three languages: - Accept-Language: it - Messages in Italian (default) - Accept-Language: en - Messages in English - Accept-Language: de - Messages in German

Regional variants are supported and automatically mapped to the base language (e.g., de-DE, de-AT, de-CH → de). For more details, see the localization documentation.

v1.0.20 - January 4, 2026

Breaking Changes

Localization Header - Migration to Accept-Language

The localization header has been migrated from the custom Invoicetronic-Language header to the standard HTTP Accept-Language header (RFC 7231). For more details, see the localization documentation.

Action required: Clients must update their integrations to use the Accept-Language header instead of Invoicetronic-Language: - Before: Invoicetronic-Language: en - Now: Accept-Language: en

The custom Invoicetronic-Language header is no longer supported. The default language is now Italian (previously it was English).

New Features

Full multi-language support

All validation error messages are now available in Italian and English. The API responds in the language specified in the Accept-Language header: - Accept-Language: it - Messages in Italian - Accept-Language: en - Messages in English

If the header is absent or contains an unsupported language, the API will respond in Italian. Currently supported languages: Italian (it), English (en).

v1.0.19 - January 2, 2026

Bug Fixes

Log Errors - More Readable error Field

Improved the error field in logs to show only the actual error message instead of the entire JSON response. The field now contains the real error message (e.g., "vat is required") instead of the full JSON wrapper, making logs more readable. For ProblemDetails errors, the detail field is extracted; otherwise, the title field is used, or for non-ProblemDetails responses, the raw response body (truncated to 500 characters).

v1.0.18 - January 1, 2026

Bug Fixes

Required field validation

Fixed required field validation to return 400 Bad Request instead of 500 Internal Server Error when vat, fiscal_code, name (Company) or payload (Send/Receive) are null. These fields were already marked as required in the API contract and OpenAPI specification, but the validation was not properly enforced at runtime.

v1.0.16 - December 9, 2025

Changes

Invoice Submission - DatiTrasmissione Auto-population

When submitting an invoice without specifying the file_name field, the system now automatically updates the DatiTrasmissione fields in the XML if they are empty: - IdTrasmittente.IdPaese is set to "IT" - IdTrasmittente.IdCodice is set to "01180680397" (Invoicetronic VAT number) - ProgressivoInvio is set to the auto-generated Base36 counter

Previously, only the filename was auto-generated but the XML content remained unchanged. This change ensures consistency between the filename and the XML structure. Existing non-empty values are always preserved and never overwritten.

v1.0.15 - December 6, 2025

New Features

Invoicetronic-Version Header

Added Invoicetronic-Version header to all API responses. Clients can now verify the API version and detect updates by reading this header from any response. The version number matches the API release version (e.g., "1.0.15").

v1.0.14 - December 6, 2025

Bug Fixes

Webhook - Payload Encoding

Fixed webhook payload encoding from UTF-16 to UTF-8 for correct HMAC signature verification. The webhook HTTP payload was being sent with Encoding.Unicode (UTF-16LE) while the HMAC signature was computed using ASCII encoding, making it difficult for clients to verify the signature. Now both payload and HMAC computation use UTF-8 encoding, which is the standard for JSON payloads and ensures consistent signature verification.

v1.0.13 - December 5, 2025

Bug Fixes

Webhook - Wildcard event support

Fixed support for the wildcard event (*) in webhooks. Webhooks configured with the * event were accepted during creation but were never triggered. Now webhooks with * in their events list are correctly triggered for all events.

SDK v1.1 / API v1.0.12 - December 4, 2025

New Features

Webhook - resource_id field

Added resource_id field to webhook notifications. Webhook payloads now include the ID of the resource created or modified by the request.

For example, for update.add events, the resource_id field contains the ID of the newly created Update entity. This allows webhook receivers to directly fetch resource details without having to match based on timestamps or other heuristics.

v1.0.9 - December 4, 2025

Bug Fixes

Webhook notifications for receive.add and update.add

Fixed an issue that prevented webhook notifications from being sent correctly for receive.add and update.add events. Webhooks are now correctly triggered for the resource owner.

v1.0.7 - December 3, 2025

Bug Fixes

Webhook notifications with null company_id

Fixed an issue that prevented webhook notifications from being sent when the API response contained a null company_id value. Webhooks are now correctly sent even in these cases.

SDK v1.0 / API v1.0.0 - July 14, 2025

New Features

First official release of Invoicetronic API with full SDK support for 8 languages: C#, Python, PHP, Java, JavaScript, Ruby, Go, TypeScript.