---
agentTools:
  projectIndex: https://developers.ampeco.com/llms.txt
---

# 3.252.0 release notes

1. ⚠️ **Breaking changes**
   1. Changed validation on `POST /public-api/actions/session/v1.0/{session}/change-tariff` so that `tariffId` must reference a tariff with usable concrete pricing. Unresolved markup or discount tariff definitions now produce a `422` validation error.
   2. Made provider-specific configuration properties mandatory when creating a payment terminal, or when changing its integration, on `POST /public-api/resources/payment-terminals/v1.0`, `PATCH` and `PUT /public-api/resources/payment-terminals/v1.0/{paymentTerminal}`, and their v1.1 equivalents. Requests must provide the required fields for the selected terminal type, such as `phone`, `defaultLanguage`, `info`, `presentCardOnStopSession`, `verificationCode`, `serialNumber`, or `terminalId`.
   3. Changed `partnerId` validation for user-group writes. On `POST /public-api/resources/user-groups/v1.0`, `PATCH /public-api/resources/user-groups/v1.0/{userGroup}`, and `PUT /public-api/resources/user-groups/v1.0/{userGroup}`, the field is now required for administrators whose scope requires a partner assignment and must reference a partner they may assign.
2. ✨ **New features**
   4\. Added `GET /public-api/resources/ocpi-commands/v1.0` and `GET /public-api/resources/ocpi-commands/v1.0/{ocpiCommand}` for retrieving commands received from eMSPs over OCPI. The listing supports filtering by `roamingConnectionId`, `type`, `result`, `failureReason`, `createdAfter`, and `createdBefore`.
   5\. Added optional tariff session-limit properties: `stopSession.stopWhenPreAuthorizedAmountFallsBelow`, `stopSession.autoStopAmount`, and `startSessionRestrictions.minimumBalance`. They are available when creating or updating tariffs through `POST /public-api/resources/tariffs/v1.0`, `PATCH` and `PUT /public-api/resources/tariffs/v1.0/{tariff}`, and in responses from those endpoints, `GET /public-api/resources/tariffs/v1.0`, `GET /public-api/resources/tariffs/v1.0/{tariff}`, and `GET /public-api/resources/tariff-snapshots/v1.0/{tariffSnapshot}`.
   6\. Added `PUT /public-api/resources/user-groups/v1.0/{userGroup}` to replace a user group with a complete representation. Writable properties omitted from the request are reset; use `PATCH` to update only selected properties.
3. 🔧 **Improvements**
   7\. Expanded `rejectedPaymentMethodErrorCode` responses from `POST /public-api/actions/charge-point/v1.0/{chargePoint}/start/{evse}` and `POST /public-api/actions/evse/v1.0/{evse}/start` with corporate-billing rejection values for unavailable ad-hoc tariffs, unsupported charger types, cross-operator opt-in, currency mismatches, unavailable exchange rates, exceeded limits, and uncovered locations.
   8\. Expanded `corporateBilling.restrictionCause` on Session responses from `GET /public-api/resources/sessions/v1.0`, `GET /public-api/resources/sessions/v1.0/{session}`, and `POST /public-api/actions/session/v1.0/{session}/set-custom-fields` with `cross_operator_not_opted_in` and `exchange_rate_unavailable`.
   9\. Added a `424 Failed Dependency` response to `POST /public-api/resources/transactions/v1.0` and `PATCH /public-api/resources/transactions/v1.0/{transaction}` when a transaction cannot be finalized because a corporate-billing amount cannot be converted due to an unavailable exchange rate.
   10\. Changed payment-terminal responses to return safe empty or `false` defaults for missing provider configuration rather than failing to return the terminal, on `/public-api/resources/payment-terminals/v1.0` and `/public-api/resources/payment-terminals/v1.1` endpoints.
   11\. Changed `PATCH /public-api/resources/users/v1.0/{user}/payment-methods/{paymentMethodId}` to correctly update the payment method associated with the specified subscription installment, including installments other than the current one.