3.284.0 release notes
about 8 hours ago by ReadMe API
- ⚠️ Breaking changes
- Changed date validation on
POST /public-api/resources/partner-contracts/v1.0andPATCH/PUT /public-api/resources/partner-contracts/v1.0/{partnerContract}to reject anendDatebeforestartDatewith422. The check applies when creating a contract or changing dates on a contract that has not ended. - Changed
filter[origin]validation onGET /public-api/resources/partner-expenses/v1.1andGET /public-api/resources/partner-revenues/v1.1to reject unsupported origin values instead of accepting arbitrary strings.
- Changed date validation on
- ✨ New features
- Added
roaming_connectionas a circuit user prioritytypeonPOST /public-api/resources/circuits/v2.0/{circuit}/user-prioritiesandPATCH /public-api/resources/circuits/v2.0/{circuit}/user-priorities/USERPRIORITY. SettargetIdto an eligible roaming connection ID, omit it on creation to cover all roaming connections, or sendnullon update to cover all roaming connections; responses omittargetIdfor an all-connections priority. - Added the optional
afirLabellingLetterresponse field to connectors, identifying the applicable AFIR compatibility label when available. It is returned byGET/POST /public-api/resources/charge-points/v2.0/{chargePoint}/evses,GET/PATCH /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse},GET/POST /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}/connectors,GET/PATCH /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}/connectors/{connector},GET/POST /public-api/resources/evses/v2.1,GET/PATCH /public-api/resources/evses/v2.1/{evse}, andPOST /public-api/actions/evse/v1.0/{evse}/set-custom-fields. - Added the optional
reimbursement.fixedAmountPerPeriodEnabledsetting toPOST /public-api/resources/partner-contracts/v1.0andPATCH/PUT /public-api/resources/partner-contracts/v1.0/{partnerContract}to enable fixed payments per reimbursement period. The setting is also returned, when reimbursement is enabled, by those endpoints,GET /public-api/resources/partner-contracts/v1.0,GET /public-api/resources/partner-contracts/v1.0/{partnerContract}, andPOST /public-api/actions/partner-contract/v1.0/{partnerContract}/disable,POST /public-api/actions/partner-contract/v1.0/{partnerContract}/reactivate, andPOST /public-api/actions/partner-contract/v1.0/{partnerContract}/start-offboarding. - Added the optional
fixedAmountPerPeriodfield to requests onPOST /public-api/resources/reimbursement-policies/v1.0andPATCH /public-api/resources/reimbursement-policies/v1.0/{reimbursementPolicy}, and to responses from those endpoints andGET /public-api/resources/reimbursement-policies/v1.0andGET /public-api/resources/reimbursement-policies/v1.0/{reimbursementPolicy}. It specifies a non-negative payment to the driver in addition to energy reimbursement; non-zero amounts require fixed payments to be enabled on the applicable partner contract or operator settings, and sendingnullon update removes the amount. - Added
partnerCurrencyto responses fromGET /public-api/resources/partner-settlement-reports/v1.1andGET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}for eligible cross-operator reports with a stored exchange rate. It containscurrencyCode,conversionRate, and convertedtotals;subtotalsand other amounts remain in the report currency. - Added
subtotals.expenses.homeChargingReimbursementAdminFeeandsubtotals.revenues.homeChargingReimbursementAdminFeeRefundto responses fromGET /public-api/resources/partner-settlement-reports/v1.1andGET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}when the report contains the corresponding records.
- Added
- 🔧 Improvements
- Expanded expense response
originvalues withhome_charging_reimbursement_admin_feeonGET /public-api/resources/partner-expenses/v1.1,GET /public-api/resources/partner-expenses/v1.2, andPOST /public-api/actions/partner-expense/v1.0/{partnerExpense}/set-custom-fields; expanded revenue responseoriginvalues withhome_charging_reimbursement_admin_fee_refundonGET /public-api/resources/partner-revenues/v1.1,GET /public-api/resources/partner-revenues/v1.2, andPOST /public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields. The respective new values are also accepted byfilter[origin]on thev1.2listing endpoints. - Changed partial updates on
PATCH /public-api/resources/circuits/v2.0/{circuit}/user-priorities/USERPRIORITYto preserve omittedtype,targetId, andpriorityvalues when the type is unchanged. Changingtypediscards the previous target, so switching topartneroruserGrouprequires a newtargetId. - Added
409 Conflictresponses for duplicate roaming connection priorities onPOST /public-api/resources/circuits/v2.0/{circuit}/user-prioritiesandPATCH /public-api/resources/circuits/v2.0/{circuit}/user-priorities/USERPRIORITY. - Changed the
enabledresponse field to reflect whether the roaming operator is enabled in the CPO role onGET /public-api/resources/roaming-cpos/v1.0,GET/PATCH /public-api/resources/roaming-cpos/v1.0/{roamingCpo},GET /public-api/resources/roaming-operators/v2.0, andGET/PATCH /public-api/resources/roaming-operators/v2.0/{roamingOperator}. - Changed invoice locale fallback to prefer the configured invoice language before the operator's default locale when no explicit locale is supplied for invoice details on
POST /public-api/resources/transactions/v1.0andPOST /public-api/actions/evse/v1.0/{evse}/start-ad-hoc-session. Invoice issuance throughPOST /public-api/actions/transactions/v1.0/{transaction}/issue-invoicealso uses this fallback when no user locale is available. - Added a
404 Not Foundresponse toPATCH /public-api/resources/charge-points/v1.0/{chargePoint}/configurations/{key}when the configuration key does not exist, including aQRCode0key that the charge point refused when a configuration template attempted to create it.
- Expanded expense response
