3.243.0 release notes
about 3 hours ago by ReadMe API
- ⚠️ Breaking changes
- Changed validation for the optional
userManualfield onPOST /public-api/resources/models/v1.0andPATCH /public-api/resources/models/v1.0/{model}: URLs must now usehttporhttpsand be no longer than 500 characters. Existing clients that send other URL schemes or longer values must update.
- Changed validation for the optional
- ✨ New features
- Added the optional
powerSharingobject to Charge point requests and responses onGETandPOST /public-api/resources/charge-points/v2.0andGETandPATCH /public-api/resources/charge-points/v2.0/{chargePoint}. It supports DC cabinet power-sharing configuration throughenabled,managementMode,totalCabinetPowerKw, andmoduleSizeKw. - Added the optional
installerManualfield to Charge point model create and update requests onPOST /public-api/resources/models/v1.0andPATCH /public-api/resources/models/v1.0/{model}. Provide an HTTP or HTTPS URL, ornullto clear the field. - Added the optional
customFieldsobject to Session responses fromGET /public-api/resources/sessions/v1.0andGET /public-api/resources/sessions/v1.0/{session}. It returns applicable custom field values keyed by their configured identifiers.
- Added the optional
- 🔧 Improvements
- Expanded the
subscriptionBillingPeriodIdfilter and response behavior forGET /public-api/resources/transactions/v1.0and Transaction responses. The API now finds and identifies transactions associated with a subscription billing period through either the transaction itself or its payment method. - Made the optional
userManualfield nullable on Charge point model create and update requests, allowing clients to clear an existing value withnull.
- Expanded the
