HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog

3.282.0 release notes

  1. ⚠️ Breaking changes
    1. Changed DELETE /public-api/resources/configuration-templates/v1.0/{template} to return 409 Conflict with a message when the template has pending applications waiting for charge points to become idle. Wait for those applications to complete or apply another template to replace them before deleting.
  2. ✨ New features
    1. Added the optional executionTime request field to POST /public-api/actions/configuration-template/v1.0/{template}/apply-to-charge-points, accepting immediately (default) or when_idle. Selecting when_idle defers the configuration push and reset until no charging sessions are running, for up to 24 hours; when resetType is none, the configuration is always applied immediately.
    2. Added include[]=effectivePreAuthorization to GET /public-api/resources/tariffs/v1.0/{tariff} to return applicable effective values: pricing.effectivePreAuthorizeAmount, pricing.effectiveIncrementalPreAuthorizationAmount, stopSession.effectiveStopWhenPreAuthorizedAmountFallsBelow, stopSession.effectiveAutoStopAmount, startSessionRestrictions.effectiveMinimumBalance, and restrictions.effectiveAdHocStopWhenPreAuthorizedAmountFallsBelow. These values account for tariff overrides and applicable billing defaults, and can change with billing settings without updating lastUpdatedAt or triggering a tariff webhook.
  3. 🔧 Improvements
    1. Changed PATCH /public-api/resources/partner-contracts/v1.0/{partnerContract} to preserve existing values for omitted fields, including nested settings, so partial updates do not require resending unchanged contract details.
    2. Expanded the filter[editTypes] query parameter on GET /public-api/resources/sessions/v1.0 to accept session_times_corrected, and the response type field on GET /public-api/resources/sessions/v1.0/{session}/edits to return the same value. Clients that enumerate edit types should handle this additional value.
    3. Expanded the response tariffs[].type and tariffs[].pricingType values on GET /public-api/resources/evses/v2.1/{evse}/effective-tariffs to include markup_and_discount. Clients that enumerate tariff types should handle this additional value.