3.270.0 release notes
about 2 hours ago by ReadMe API
- ⚠️ Breaking changes
- Changed
passwordvalidation to reject null characters (\u0000) onPOST /public-api/resources/partners/v2.0/{partner}/adminsandPATCH /public-api/resources/partners/v2.0/{partner}/admins/{admin}. - Changed downtime creation validation to require a
chargePointIdorevseIdaccessible to the authenticated administrator onPOST /public-api/resources/charge-point-downtime-periods/v1.0andPOST /public-api/resources/evse-downtime-periods/v1.0, respectively. Requests referencing resources outside the administrator's access now fail validation. - Removed
roaming_evse_not_supportedfromdata.emptyReasonon the experimentalGET /public-api/resources/evses/v2.1/{evse}/effective-tariffsendpoint. Roaming EVSEs now return applicable tariffs or another empty reason instead.
- Changed
- ✨ New features
- Added support for effective tariffs at EVSEs received through OCPI or Hubject roaming on
GET /public-api/resources/evses/v2.1/{evse}/effective-tariffs. Roaming-based markup and discount prices usepricingType: pricing_basedandpricing.priceElements, withpriceComponentscontainingtype,priceandstepSize, plus optionalconditionsdescribing when each element applies. - Added
roaming_tariffas aderivedFrom[].typevalue and the optionalderivedFrom[].roamingTariffIdfield onGET /public-api/resources/evses/v2.1/{evse}/effective-tariffs. The identifier matches an entry inroamingIdson the roaming tariffs resource, allowing consumers to identify the source of a calculated price.
- Added support for effective tariffs at EVSEs received through OCPI or Hubject roaming on
- 🔧 Improvements
- Changed
roamingTariffHumanReadableto return decoded characters rather than HTML entities in roaming tariff responses onGET /public-api/resources/roaming-tariffs/v2.0andGET /public-api/resources/roaming-tariffs/v2.0/{roamingTariff}.
- Changed
