HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog

3.242.0 release notes

  1. ⚠️ Breaking changes
    1. Removed the pin property from Charge point responses when calls to GET or POST /public-api/resources/charge-points/v1.0 and /public-api/resources/charge-points/v2.0, or GET or PATCH /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.
    2. Changed evses[].tariffGroupId validation on POST /public-api/resources/charge-points/v1.0, PATCH /public-api/resources/charge-points/v1.0/{chargePoint}, POST /public-api/resources/charge-points/v2.0, and PATCH /public-api/resources/charge-points/v2.0/{chargePoint} to accept only tariff groups belonging to the relevant operator.
    3. Made POST /public-api/resources/charge-points/v2.0/{chargePoint}/smart-charging require permission to control smart charging. Tokens without that permission now receive 403.
    4. Restricted POST /public-api/actions/installer-job/v1.0/{installerJob}/assign-charge-points to charge points accessible to the calling user. Requests that select only inaccessible charge points now fail instead of assigning them.
    5. 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.
    6. Removed totalAmount from charging-period objects in Session responses from GET /public-api/resources/sessions/v1.0 and GET /public-api/resources/sessions/v1.0/{session} when the period has no total amount. Consumers must handle the property being absent.
  2. New features
    1. Added locale-specific Partner fields: translatedName, translatedAddress, translatedCity, and translatedRegion, plus bankDetails.translatedBankName, bankDetails.translatedBankAddress, and bankDetails.translatedBankAccountHolder. They are available in requests to POST /public-api/resources/partners/v2.0 and PATCH /public-api/resources/partners/v2.0/{partner}, and in responses from those endpoints and GET /public-api/resources/partners/v2.0 and GET /public-api/resources/partners/v2.0/{partner}.
    2. 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. translatedName must include an English (en) entry when supplied.
  3. 🔧 Improvements
    1. Changed the deprecated Partner response fields name, address, and city to return their English translation when available, then fall back to the operator's default locale and the originally stored value, on GET /public-api/resources/partners/v2.0 and GET /public-api/resources/partners/v2.0/{partner}.
    2. Changed PATCH /public-api/resources/charge-points/v2.0/{chargePoint} to preserve a Charge point's existing pin when the request omits that property.
    3. Changed idTag in Session responses from GET /public-api/resources/sessions/v1.0 and GET /public-api/resources/sessions/v1.0/{session} to return a usable remote-start identifier for affected Hubject roaming sessions instead of serialized identification data.
    4. Expanded access to POST /public-api/actions/charge-point/v1.0/{chargePoint}/reset-security-profile so a token with either charge-point maintenance permission or reset-security-profile permission can perform the action.
  4. 🗑️ Deprecations
    1. Deprecated the single-language Partner fields name, address, city, and region in requests and responses on POST /public-api/resources/partners/v2.0, PATCH /public-api/resources/partners/v2.0/{partner}, GET /public-api/resources/partners/v2.0, and GET /public-api/resources/partners/v2.0/{partner}. Use their corresponding translated* fields instead.
    2. Deprecated bankDetails.bankName, bankDetails.bankAddress, and bankDetails.bankAccountHolder on the same Partner endpoints. Use bankDetails.translatedBankName, bankDetails.translatedBankAddress, and bankDetails.translatedBankAccountHolder instead.