3.242.0 release notes
about 1 hour ago by ReadMe API
- ⚠️ Breaking changes
- Removed the
pinproperty from Charge point responses when calls toGETorPOST/public-api/resources/charge-points/v1.0and/public-api/resources/charge-points/v2.0, orGETorPATCH/public-api/resources/charge-points/v1.0/{chargePoint}and/public-api/resources/charge-points/v2.0/{chargePoint}, are authenticated with an installer token. Installer integrations must no longer rely on a PIN being returned. - Changed
evses[].tariffGroupIdvalidation onPOST/public-api/resources/charge-points/v1.0,PATCH/public-api/resources/charge-points/v1.0/{chargePoint},POST/public-api/resources/charge-points/v2.0, andPATCH/public-api/resources/charge-points/v2.0/{chargePoint}to accept only tariff groups belonging to the relevant operator. - Made
POST/public-api/resources/charge-points/v2.0/{chargePoint}/smart-chargingrequire permission to control smart charging. Tokens without that permission now receive403. - Restricted
POST/public-api/actions/installer-job/v1.0/{installerJob}/assign-charge-pointsto charge points accessible to the calling user. Requests that select only inaccessible charge points now fail instead of assigning them. - Prevented installation and maintenance company users from reopening completed or failed installer jobs through
POST/public-api/actions/installer-job/v1.0/{installerJob}/change-status. - Removed
totalAmountfrom charging-period objects in Session responses fromGET/public-api/resources/sessions/v1.0andGET/public-api/resources/sessions/v1.0/{session}when the period has no total amount. Consumers must handle the property being absent.
- Removed the
- ✨ New features
- Added locale-specific Partner fields:
translatedName,translatedAddress,translatedCity, andtranslatedRegion, plusbankDetails.translatedBankName,bankDetails.translatedBankAddress, andbankDetails.translatedBankAccountHolder. They are available in requests toPOST/public-api/resources/partners/v2.0andPATCH/public-api/resources/partners/v2.0/{partner}, and in responses from those endpoints andGET/public-api/resources/partners/v2.0andGET/public-api/resources/partners/v2.0/{partner}. - Added validation for translated Partner fields so each value is submitted as a locale-and-translation array, and cannot be sent together with its deprecated single-language counterpart.
translatedNamemust include an English (en) entry when supplied.
- Added locale-specific Partner fields:
- 🔧 Improvements
- Changed the deprecated Partner response fields
name,address, andcityto return their English translation when available, then fall back to the operator's default locale and the originally stored value, onGET/public-api/resources/partners/v2.0andGET/public-api/resources/partners/v2.0/{partner}. - Changed
PATCH/public-api/resources/charge-points/v2.0/{chargePoint}to preserve a Charge point's existingpinwhen the request omits that property. - Changed
idTagin Session responses fromGET/public-api/resources/sessions/v1.0andGET/public-api/resources/sessions/v1.0/{session}to return a usable remote-start identifier for affected Hubject roaming sessions instead of serialized identification data. - Expanded access to
POST/public-api/actions/charge-point/v1.0/{chargePoint}/reset-security-profileso a token with either charge-point maintenance permission or reset-security-profile permission can perform the action.
- Changed the deprecated Partner response fields
- 🗑️ Deprecations
- Deprecated the single-language Partner fields
name,address,city, andregionin requests and responses onPOST/public-api/resources/partners/v2.0,PATCH/public-api/resources/partners/v2.0/{partner},GET/public-api/resources/partners/v2.0, andGET/public-api/resources/partners/v2.0/{partner}. Use their correspondingtranslated*fields instead. - Deprecated
bankDetails.bankName,bankDetails.bankAddress, andbankDetails.bankAccountHolderon the same Partner endpoints. UsebankDetails.translatedBankName,bankDetails.translatedBankAddress, andbankDetails.translatedBankAccountHolderinstead.
- Deprecated the single-language Partner fields
