3.195.0 release notes

✨ New features
1. Added a new endpoint POST /public-api/actions/circuit/v2.0/{circuit}/set-session-boost/{session} for toggling boost mode on an active session within a DLM circuit. The request body requires an enabled boolean field. The endpoint returns 202 Accepted.
2. Added the new optional resetType field to POST /public-api/actions/configuration-template/v1.0/{template}/apply-to-charge-points. When omitted, a soft reset is applied by default.
3. Added chargingProfile as a valid value for the include query parameter on GET /public-api/resources/sessions/v1.0/{session}. When included, the response contains the session's active DLM charging profile data.
🔧 Improvements
1. Made the status field optional on Location update requests. Consumers can now omit status when updating a location via PUT or PATCH on /public-api/resources/locations/v2.0/{location}.
2. Valina payment terminal screensaver fields (screensaverWelcomeMessage, screensaverPaymentMethods, screensaverLogoUrl) returned by GET /public-api/resources/payment-terminals/v1.1 and GET /public-api/resources/payment-terminals/v1.1/{terminal} now fall back to integration-level defaults when not configured at the individual terminal level, instead of returning empty values.
3. POST /public-api/resources/transactions/v1.0 now accepts sessions that were authorized via OCPP (charge-point-initiated authorization), in addition to sessions authorized by the API consumer or a third-party authority. This expands the range of sessions eligible for manual transaction creation.
4. Improved PATCH /public-api/resources/tariffs/v1.0/{tariff} merge behavior for deprecated display fields: patching display.priceInformation without display.priceInformationLocalized in the same request now correctly clears the localized variant from the effective tariff data, and similarly for display.totalCostInformation. This ensures the patched deprecated field takes effect as expected.