⚠️ Breaking changes
1. Changed the hardwareStatus response field on charge point, EVSE, and hardware downtime resources to use hardware-only status values instead of broader operational status values. Clients should no longer expect values such as available, charging, preparing, reserved, suspendedEV, suspendedEVSE, finishing, faulted, or unavailable on these fields.
2. Changed the errorCode returned by POST /public-api/actions/charge-point/v1.0/{chargePoint}/start/{evse} and POST /public-api/actions/evse/v1.0/{evse}/start for corporate billing failures to API response codes. Clients should now expect corporate_billing_policy_inactive and corporate_billing_limit_exceeded instead of enum-style names.
✨ New features
1. Added the optional paymentMetadata request property to POST /public-api/resources/transactions/v1.0 and PATCH /public-api/resources/transactions/v1.0/{transaction}. This object supports applicationIdentifier, terminalIdentifier, merchantIdentifier, authorisationCode, acquirerIdentifier, and cardholderVerificationMethod.
2. Added the optional paymentMetadata and paymentProcessorId response properties to GET /public-api/resources/transactions/v1.0, POST /public-api/resources/transactions/v1.0, GET /public-api/resources/transactions/v1.0/{transaction}, and PATCH /public-api/resources/transactions/v1.0/{transaction}.
3. Added the optional filter[status] query parameter to GET /public-api/resources/charge-points/v2.0/{chargePoint}/hardware-status-logs and GET /public-api/resources/evses/v2.0/{evse}/hardware-status-logs so clients can filter hardware status history by status value.
4. Added the optional terminalId, terminalModel, currentBundleVersion, and lastCertifiedAppVersion fields to PATCH /public-api/resources/payment-terminals/v1.1/{paymentTerminal} for supported terminal types.
5. Added the optional terminalId, terminalModel, currentBundleVersion, and lastCertifiedAppVersion response fields to POST /public-api/resources/payment-terminals/v1.1, GET /public-api/resources/payment-terminals/v1.1/{paymentTerminal}, and PATCH /public-api/resources/payment-terminals/v1.1/{paymentTerminal} for supported terminal types.
🔧 Improvements
1. Made hardwareStatus nullable on GET /public-api/resources/evses/v2.0 and GET /public-api/resources/evses/v2.0/{evse} so responses can represent EVSEs that do not currently have a hardware status.
2. Changed GET /public-api/resources/partner-invites/v1.0, POST /public-api/resources/partner-invites/v1.0, GET /public-api/resources/partner-invites/v1.0/{partnerInvite}, and PATCH /public-api/resources/partner-invites/v1.0/{partnerInvite} so limitCorporateAccountBillingToPartnerChargePoints and corporateBillingLimit reflect the latest corporate billing policy snapshot when one is attached to the invite.

Changelog