HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog

3.145.0 release notes

  1. New features
    1. Added the POST /actions/tax/v1.0/validate-vat endpoint for validating EU VAT numbers against the VIES service. Accepts required countryCode (2-character string) and vatNumber (string) fields, and returns validation details on success.
    2. Added the PATCH /resources/partner-contracts/v1.0/{partnerContract} endpoint for partial updates to partner contracts. Unlike PUT, this allows updating individual fields without providing all required fields.
    3. Added the optional locale request property to POST /actions/transactions/v1.0/{transaction}/issue-invoice. When provided, the invoice is issued in the specified locale.
    4. Added the optional allowChargingOutsideWorkingHours property to the workingHours object on Location v2.0 endpoints. This field appears in responses from GET /resources/locations/v2.0, GET /resources/locations/v2.0/{location}, and can be set in requests to POST /resources/locations/v2.0 and PATCH /resources/locations/v2.0/{location}.
    5. Added the optional companyName property to User endpoints. The field is returned in responses and accepted as an optional company_name request property on POST /resources/users/v1.0, PATCH /resources/users/v1.0/{user}, and the corresponding v1.1 endpoints.
    6. Added FirmwareStatusNotification as a new subscribable webhook notification type on POST /notifications/v1.0, PUT /notifications/v1.0/{notification}, POST /notifications/v2.0, and PUT /notifications/v2.0/{notification}. The callback payload includes firmware update status details and varies based on the OCPP protocol version (1.5, 1.6, or 2.0.1).
    7. Expanded the resourceType enum in Issue responses to include integration as a new value. This value may appear in the keyResource.resourceType and relatedResources fields on GET /resources/issues/v1.0, POST /resources/issues/v1.0, GET /resources/issues/v1.0/{issue}, and PATCH /resources/issues/v1.0/{issue}.
  2. 🔧 Improvements
    1. Made Issue endpoint responses more resilient to unknown resource types. Issues referencing resources with unmapped types now omit those references from the response instead of causing errors.