HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog
Terms of Use
Back to All

3.280.0 release notes

about 4 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Removed POST /public-api/actions/roaming-emsp/v1.0/{countryCode}/{partyId}/activate-broker-routing and POST /public-api/actions/roaming-emsp/v1.0/{countryCode}/{partyId}/deactivate-broker-routing.
  2. ✨ New features
    1. Added the experimental POST /public-api/actions/evse/v1.0/{evse}/start-ad-hoc-session endpoint to create an ad hoc charging session and return its sessionId and payment checkout, containing either a redirectUrl or a clientSecret. The endpoint accepts paymentMethod and invoiceDetails, requires returnUrl for Worldline and Adyen, and starts charging once payment is confirmed.
    2. Added the read-only networkStatus response field with values never_connected, online, and offline to GET and POST /public-api/resources/electricity-meters/v1.0, and GET and PATCH /public-api/resources/electricity-meters/v1.0/{electricityMeter}.
    3. Added the optional deductedFees response object to GET /public-api/resources/partner-revenues/v1.2 and POST /public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields, breaking down per-session, per-kWh, and handling fees deducted before calculating the partner's share. The object is omitted when no fees were deducted or the fees are recorded as partner expenses.
  3. 🔧 Improvements
    1. Expanded the accepted type values with SignV2G20Certificate on POST /public-api/actions/charge-point/v1.0/{chargePoint}/trigger-message and POST /public-api/actions/evse/v1.0/{evse}/trigger-message.
    2. Expanded the accepted certificateType values with OEMRootCertificate on POST /public-api/actions/charge-point/v2.0/{chargePoint}/delete-certificate, POST /public-api/actions/charge-point/v2.0/{chargePoint}/install-certificate, and POST /public-api/actions/charge-point/v2.0/{chargePoint}/sync-certificates, and with V2G20Certificate on the delete-certificate endpoint.
    3. Expanded Issue resource references to support notification in keyResource.resourceType on GET and POST /public-api/resources/issues/v1.0, and GET and PATCH /public-api/resources/issues/v1.0/{issue}, as well as in relatedResources[].resourceType on the single-issue read endpoint. The Issues listing also accepts notification in filter[keyResourceType].
    4. Expanded the state response values and filter[state] options with declining_volume on GET /public-api/resources/usage-states/v1.0.
    5. Changed partners[].name on GET /public-api/resources/usage-states/v1.0 to return the partner's business name instead of its English display name, including when no English display name is available.
    6. Changed POST /public-api/actions/charge-point/v1.0/{chargePoint}/clear-charging-profile to return 409 Conflict with an explanatory message when the charge point has no network protocol configured.
    7. Expanded userId validation on POST /public-api/actions/charge-point/v1.0/{chargePoint}/reserve/{evse} to allow administrators without an operator assignment to reserve for users within their permitted scope.
    8. Changed hardware status log listings on GET /public-api/resources/charge-points/v2.0/{chargePoint}/hardware-status-logs and GET /public-api/resources/evses/v2.0/{evse}/hardware-status-logs to return entries in ascending creation-time order, using the ID to order entries with the same timestamp. Previously issued pagination cursors remain supported.
    9. Changed duplicate currency-pair handling on POST /public-api/resources/currency-rates/v1.0 to return a validation error for base even when concurrent requests attempt to create the same pair.
    10. Changed EVSE assignment validation on PUT /public-api/resources/parking-spaces/v1.0/{parkingSpace}/evses to return a validation error for evses, rather than a server error, when the associated charging zone cannot be found.
    11. Expanded churnReason.reasonId validation on POST /public-api/actions/partner/v1.0/{partner}/start-offboarding and POST /public-api/actions/partner/v1.0/{partner}/disable to accept the reason recorded for the partner's latest exit, even when that reason is no longer selectable.