HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog
Terms of Use
Start typing to search…
Back to All

3.166.0 release notes

about 2 hours ago by ReadMe API
  1. ✨ New features
    1. Added POST /public-api/actions/charge-point/v1.0/{chargePoint}/check-tariff-display-support endpoint. Probes whether an OCPP 1.6 charge point supports tariff display messages, with an optional enableIfSupported parameter to automatically enable the capability.
    2. Added the optional tariffDisplayMessages object to Charge Point responses on GET /public-api/resources/charge-points/v2.0, POST /public-api/resources/charge-points/v2.0, GET /public-api/resources/charge-points/v2.0/{chargePoint}, and PATCH /public-api/resources/charge-points/v2.0/{chargePoint}. The object contains sendDefaultPrice, sendUserPrice, sendRunningCost, and sendFinalCost boolean fields controlling which tariff display message types are sent.
    3. Added the optional tariffDisplayMessages request property on PATCH /public-api/resources/charge-points/v2.0/{chargePoint} to configure tariff display message settings.
    4. Added the optional accessAndPermissions.createFromTemplate and accessAndPermissions.changeSystemStatus boolean fields to Partner Contract requests and responses on GET /public-api/resources/partner-contracts/v1.0, POST /public-api/resources/partner-contracts/v1.0, GET /public-api/resources/partner-contracts/v1.0/{partnerContract}, PATCH /public-api/resources/partner-contracts/v1.0/{partnerContract}, and PUT /public-api/resources/partner-contracts/v1.0/{partnerContract}. These control whether the partner can create charge points from templates and change system status.
  2. 🔧 Improvements
    1. Made the operatorId response property always present (required) on Subscription Plan endpoints: GET /public-api/resources/subscription-plans/v2.0, POST /public-api/resources/subscription-plans/v2.0, GET /public-api/resources/subscription-plans/v2.0/{subscriptionPlan}, and PATCH /public-api/resources/subscription-plans/v2.0/{subscriptionPlan}. Previously this field could be absent.
    2. Improved the precision of the totalKwh field on Receipt responses to use higher-precision energy data.