3.283.0 release notes
about 14 hours ago by ReadMe API
- ⚠️ Breaking changes
- Removed
POST /public-api/actions/transaction/v1.0/{transaction}/create-pre-authorization. Consumers must stop calling this endpoint.
- Removed
- ✨ New features
- Added support for Payten Castles terminals with
terminalType: payten_castlesonGETandPOST /public-api/resources/payment-terminals/v1.1,GETandPATCH /public-api/resources/payment-terminals/v1.1/{paymentTerminal}, andPOST /public-api/actions/payment-terminal/v1.0/{paymentTerminal}/set-custom-fields. Use payment terminal resource versionv1.1for this terminal type; resource versionv1.0does not support it. - Added the optional
revenueSharing.separateElectricityCostReimbursementsetting toPOST /public-api/resources/partner-contracts/v1.0andPATCHandPUT /public-api/resources/partner-contracts/v1.0/{partnerContract}, and exposed it in their responses,GET /public-api/resources/partner-contracts/v1.0,GET /public-api/resources/partner-contracts/v1.0/{partnerContract}, and the responses fromPOST /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. When enabled, electricity cost reimbursement is reported separately from awaited and collected revenue; it requiresreimburseForElectricityCost: true, defaults tofalseon creation, and retains its current value when omitted from an update. - Added the optional
totals.electricityCostReimbursementresponse field toGET /public-api/resources/partner-settlement-reports/v1.1andGET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}for reports with separately reported electricity cost reimbursement. For these reports,totals.awaitedRevenueandtotals.collectedRevenueexclude this amount, whiletotals.revenueincludes it. - Added optional
carbonDioxideandnuclearWastefields to the request body ofPUT /public-api/resources/electricity-rates/v2.0/{electricityRate}/energy-mixand to the responses fromGETandPUTon the same path. Both measure environmental impact in g/kWh and accept values from0to999999.999999with up to six decimal places; omitting a field preserves its stored value, sendingnullclears it, and unknown values are omitted from responses. - Added
filter[userId],filter[inviteEmail],filter[acceptedAfter],filter[acceptedBefore],filter[createdAfter],filter[createdBefore],filter[lastUpdatedAfter], andfilter[lastUpdatedBefore]toGET /public-api/resources/partner-invites/v2.0. Requests using either last-updated filter return results in ascending last-updated order, with ID as the tie-breaker; requests without those filters retain newest-ID-first ordering.
- Added support for Payten Castles terminals with
- 🔧 Improvements
- Changed
POST /public-api/actions/charge-point/v1.0/{chargePoint}/get-composite-scheduleandPOST /public-api/actions/charge-point/v1.0/{chargePoint}/get-local-list-versionto return409 Conflictwith an explanatory message when the charge point has no network protocol configured. - Changed validation on
GET /public-api/resources/sessions/v1.0to recognize the correctly spelledfilter[chargePointBootNotificationSerialNumber]parameter, aligning validation with the existing serial-number filter. - Changed
filter[inviteEmail]onGET /public-api/resources/partner-invites/v1.0andGET /public-api/resources/partner-invites/v2.0to match the complete email address, including addresses containing commas. - Made
filter[partnerId],filter[corporateBillingPolicyId], andfilter[status]nullable onGET /public-api/resources/partner-invites/v2.0, allowing empty filter values instead of rejecting them during validation. - Changed partner contract validation on
POST /public-api/resources/partner-contracts/v1.0andPATCHandPUT /public-api/resources/partner-contracts/v1.0/{partnerContract}to allowrevenueSharing.reimburseForElectricityCost: falsewhenrevenueSharing.deductElectricityCostisfalse. Enabling reimbursement still requires electricity cost deduction to be enabled. - Changed authorization responses to stop presenting
accepted_type_e_socket_session_stopas a rejection reason onGET /public-api/resources/authorizations/v1.0/{authorization},GET /public-api/resources/authorizations/v2.0,GET /public-api/resources/authorizations/v2.0/{authorization},GET /public-api/resources/authorizations/v2.1, andGET /public-api/resources/authorizations/v2.1/{authorization}. For these accepted session-stop authorizations,rejectionReasonis nownullin versionsv1.0andv2.0, and omitted in versionv2.1.
- Changed
