3.225.0 release notes
about 2 hours ago by ReadMe API
- ⚠️ Breaking changes
- Removed the
invoiceStateresponse property and thefilter[invoiceState]query parameter from Partner settlement reports. Update consumers ofGET /public-api/resources/partner-settlement-reports/v1.0,GET /public-api/resources/partner-settlement-reports/v1.0/{partnerSettlementReport},POST /public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/issue-partner-invoice, andPOST /public-api/actions/partner-settlement-report/v1.0/{partnerSettlementReport}/update-external-idthat rely on this field or filter.
- Removed the
- ✨ New features
- Added
POST /public-api/actions/partner-invoice/v1.0/{partnerInvoice}/issue-credit-noteto issue a full credit note for an eligible partner invoice. The response returns the created credit note; requests for ineligible invoices return409. - Added
filter[referenceId]andfilter[type]toGET /public-api/resources/partner-invoices/v1.0, allowing consumers to find credit notes for an original invoice and filter documents byinvoiceorcredit_notetype. - Added the optional
powerOptions.maxOutputVoltageproperty to EVSE requests and responses onGETandPOST /public-api/resources/charge-points/v2.0/{chargePoint}/evses,GETandPATCH /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}, andGET,POST, andPATCH /public-api/resources/evses/v2.1. The value is an integer from 1 to 1000 volts, is supported only for DC EVSEs, and is rejected for other current types.
- Added
- 🔧 Improvements
- Added a
424response toGET /public-api/logs/communication/v1.0when communication logs are temporarily unavailable. Narrow the requested date range or retry later. - Changed billing-related Public API behavior to use the applicable operator's billing configuration, rather than a tenant-wide configuration, when resolving payment methods, payment processor requirements, subscription-plan billing types, and tariff incremental preauthorization information.
- Added a