3.144.0 release notes
20 days ago by ReadMe API
- ⚠️ Breaking changes
- Changed the deprecated field accepted by the Charge Point V2 endpoints from
autoFaultRecoverytoenableAutoFaultRecoveryonPOST /resources/charge-points/v2.0andPATCH /resources/charge-points/v2.0/{chargePoint}. Consumers using the undocumentedautoFaultRecoveryfield name with V2 endpoints must update toenableAutoFaultRecovery. This aligns the server behavior with the documented OpenAPI specification. - Added date validation on Partner Contract endpoints:
startDatemust be today or in the future when creating a contract viaPOST /resources/partner-contracts/v1.0. When updating viaPATCH /resources/partner-contracts/v1.0/{partnerContract}, the same validation applies only if thestartDatevalue is being changed. - Made
partnerIdimmutable onPATCH /resources/partner-contracts/v1.0/{partnerContract}. ThepartnerIdmust match the existing contract's partner and cannot be changed during an update.
- Changed the deprecated field accepted by the Charge Point V2 endpoints from
- ✨ New features
- Added the optional
invoiceRequiredboolean property to the Transaction request body onPOST /resources/transactions/v1.0andPATCH /resources/transactions/v1.0/{transaction}. When set totrueand the operator has receipt suppression for invoice issuance enabled, automatic receipt generation is suppressed for the transaction.
- Added the optional
- 🔧 Improvements
- Changed the Transaction
paymentMethodresponse fields (type,last4,expMonth,expYear) to fall back to stored payment data when the original payment method record is unavailable, instead of returningnull. ThepaymentMethodstring representation also falls back to stored data in this scenario. Affects all Transaction response endpoints.
- Changed the Transaction