HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog

3.283.0 release notes

  1. ⚠️ Breaking changes
    1. Removed POST /public-api/actions/transaction/v1.0/{transaction}/create-pre-authorization. Consumers must stop calling this endpoint.
  2. ✨ New features
    1. Added support for Payten Castles terminals with terminalType: payten_castles on GET and POST /public-api/resources/payment-terminals/v1.1, GET and PATCH /public-api/resources/payment-terminals/v1.1/{paymentTerminal}, and POST /public-api/actions/payment-terminal/v1.0/{paymentTerminal}/set-custom-fields. Use payment terminal resource version v1.1 for this terminal type; resource version v1.0 does not support it.
    2. Added the optional revenueSharing.separateElectricityCostReimbursement setting to POST /public-api/resources/partner-contracts/v1.0 and PATCH and PUT /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 from POST /public-api/actions/partner-contract/v1.0/{partnerContract}/disable, POST /public-api/actions/partner-contract/v1.0/{partnerContract}/reactivate, and POST /public-api/actions/partner-contract/v1.0/{partnerContract}/start-offboarding. When enabled, electricity cost reimbursement is reported separately from awaited and collected revenue; it requires reimburseForElectricityCost: true, defaults to false on creation, and retains its current value when omitted from an update.
    3. Added the optional totals.electricityCostReimbursement response field to GET /public-api/resources/partner-settlement-reports/v1.1 and GET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport} for reports with separately reported electricity cost reimbursement. For these reports, totals.awaitedRevenue and totals.collectedRevenue exclude this amount, while totals.revenue includes it.
    4. Added optional carbonDioxide and nuclearWaste fields to the request body of PUT /public-api/resources/electricity-rates/v2.0/{electricityRate}/energy-mix and to the responses from GET and PUT on the same path. Both measure environmental impact in g/kWh and accept values from 0 to 999999.999999 with up to six decimal places; omitting a field preserves its stored value, sending null clears it, and unknown values are omitted from responses.
    5. Added filter[userId], filter[inviteEmail], filter[acceptedAfter], filter[acceptedBefore], filter[createdAfter], filter[createdBefore], filter[lastUpdatedAfter], and filter[lastUpdatedBefore] to GET /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.
  3. 🔧 Improvements
    1. Changed POST /public-api/actions/charge-point/v1.0/{chargePoint}/get-composite-schedule and POST /public-api/actions/charge-point/v1.0/{chargePoint}/get-local-list-version to return 409 Conflict with an explanatory message when the charge point has no network protocol configured.
    2. Changed validation on GET /public-api/resources/sessions/v1.0 to recognize the correctly spelled filter[chargePointBootNotificationSerialNumber] parameter, aligning validation with the existing serial-number filter.
    3. Changed filter[inviteEmail] on GET /public-api/resources/partner-invites/v1.0 and GET /public-api/resources/partner-invites/v2.0 to match the complete email address, including addresses containing commas.
    4. Made filter[partnerId], filter[corporateBillingPolicyId], and filter[status] nullable on GET /public-api/resources/partner-invites/v2.0, allowing empty filter values instead of rejecting them during validation.
    5. Changed partner contract validation on POST /public-api/resources/partner-contracts/v1.0 and PATCH and PUT /public-api/resources/partner-contracts/v1.0/{partnerContract} to allow revenueSharing.reimburseForElectricityCost: false when revenueSharing.deductElectricityCost is false. Enabling reimbursement still requires electricity cost deduction to be enabled.
    6. Changed authorization responses to stop presenting accepted_type_e_socket_session_stop as a rejection reason on GET /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, and GET /public-api/resources/authorizations/v2.1/{authorization}. For these accepted session-stop authorizations, rejectionReason is now null in versions v1.0 and v2.0, and omitted in version v2.1.