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

3.258.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed include validation on GET /public-api/resources/bookings/v1.0 and GET /public-api/resources/bookings/v1.0/{booking} to require an array containing only bookedEvses. Invalid include values now return 422.
    2. Changed validation of evses.*.physicalReference on POST /public-api/resources/charge-points/v1.0, POST /public-api/resources/charge-points/v2.0, PATCH /public-api/resources/charge-points/v1.0/{chargePoint}, and PATCH /public-api/resources/charge-points/v2.0/{chargePoint} to reject duplicate new or changed references within the request and conflicts with other local EVSEs belonging to the same operator. Satellite charge point creation also checks conflicts, while allowing reuse of the corresponding master EVSE's reference.
  2. ✨ New features
    1. Added experimental administrator access management through GET /public-api/resources/admins/v1.0/{admin}/sessions, POST /public-api/actions/admin/v1.0/{admin}/terminate-sessions, and POST /public-api/actions/admin/v1.0/{admin}/end-all-access. These endpoints list active tracked browser sessions, terminate selected sessions using sessionIds, or end all browser, remembered browser, and application access without preventing a new sign-in; callers must inspect the returned outcome for all-access termination results.
    2. Added experimental partner discount scheduling through GET and POST /public-api/resources/partners/v2.0/{partner}/discount-changes, GET and PATCH /public-api/resources/partners/v2.0/{partner}/discount-changes/{discountChange}, POST /public-api/actions/partner-discount-change/v1.0/{discountChange}/cancel, and POST /public-api/actions/partner-discount-change/v1.0/{discountChange}/end-now. Consumers can schedule future corporate billing discounts, inspect their status, edit schedules, cancel changes, or end an active change immediately.
    3. Added experimental CoOperator insights through POST and GET /public-api/resources/cooperator-insights/v1.0 and GET /public-api/resources/cooperator-insights/v1.0/{insight}. Consumers can submit questions for asynchronous, read-only analysis and retrieve results by polling or subscribing to CoOperatorInsightChangedNotification; these experimental endpoints may change without a version bump.
    4. Added partner revenue custom field support: GET /public-api/resources/partner-revenues/v1.2 now returns applicable customFields and supports custom field filtering, and the experimental POST /public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields action updates their values without changing financial data. Omitted identifiers remain unchanged, while null clears a value.
    5. Added optional name and description request fields on POST /public-api/notifications/v2.0 and PUT /public-api/notifications/v2.0/{notification}, with corresponding response fields on those endpoints and on GET /public-api/notifications/v2.0 and GET /public-api/notifications/v2.0/{notification}.
    6. Added failureReason to failed booking responses on GET /public-api/resources/bookings/v1.0 and GET /public-api/resources/bookings/v1.0/{booking} when a failure reason is available.
    7. Added optional powerOptions.efficiencyPercent to EVSE requests and responses on /public-api/resources/charge-points/v2.0/{chargePoint}/evses, /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}, /public-api/resources/evses/v2.1, and /public-api/resources/evses/v2.1/{evse}. New or changed overrides for local DC EVSEs must be numeric values from 90 to 100; omission preserves an existing override, explicit null clears it on update, and AC or roaming EVSE responses omit the field.
    8. Added optional externalId to connector requests on POST /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}/connectors and PATCH /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}/connectors/{connector}. Identifiers accept strings of up to 255 characters; on update, omission preserves the identifier and null or an empty string clears it.
    9. Added the optional filter[hardwareStatus] array to GET /public-api/resources/evses/v2.1, allowing consumers to filter EVSEs by one or more hardware statuses.
    10. Added the type response field to GET /public-api/resources/reimbursement-reports/v1.0, GET /public-api/resources/reimbursement-reports/v1.0/{reimbursementReport}, and POST /public-api/actions/reimbursement-report/v1.0/{reimbursementReport}/set-custom-fields, distinguishing user and partner reports. The listing also accepts filter[type].
    11. Added optional locationId to session responses on GET /public-api/resources/sessions/v1.0, GET /public-api/resources/sessions/v1.0/{session}, and POST /public-api/actions/session/v1.0/{session}/set-custom-fields. The field is available when the charge point's location can be resolved, including deleted locations.
  3. 🔧 Improvements
    1. Expanded the notifications values to include CoOperatorInsightChangedNotification and SignedFirmwareStatusNotification on POST and GET /public-api/notifications/v2.0, PUT and GET /public-api/notifications/v2.0/{notification}, and POST /public-api/actions/notifications/v1.0/{notification}/resend.
    2. Expanded voltage values to support 600 for powerOptions.maxVoltage on /public-api/resources/charge-points/v2.0/{chargePoint}/evses, /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}, /public-api/resources/evses/v2.1, and /public-api/resources/evses/v2.1/{evse}; and for maxVoltage on /public-api/resources/evses/v2.0, /public-api/resources/evses/v2.0/{evse}, /public-api/resources/circuits/v2.0, /public-api/resources/circuits/v2.0/{circuit}, and POST /public-api/resources/charge-points/v2.0/{chargePoint}/smart-charging. Template responses on GET /public-api/resources/templates/v1.0 also support 600 for EVSE inputVoltage.
    3. Expanded partner revenue origin values and filter[origin] on GET /public-api/resources/partner-revenues/v1.2 to include home-charging-reimbursement, while retaining the existing origin values.
    4. Expanded access to GET /public-api/resources/locations/v2.0/{location} so eligible partner and sub-operator consumers with location view permission can retrieve a restricted public representation when full access is unavailable and the location has qualifying public or roaming charge points. This representation excludes administrative fields and supports only the locationImage and images includes; site managers are not eligible.
    5. Changed booking responses on GET /public-api/resources/bookings/v1.0 and GET /public-api/resources/bookings/v1.0/{booking} to return accessMethods: [] when an empty list is stored, rather than omitting the field.
    6. Expanded access policy support on POST /public-api/resources/partner-invites/v2.0 and PATCH /public-api/resources/partner-invites/v2.0/{partnerInvite} so accessPolicyId is consistently accepted and validated against policies accessible to the partner. The field is returned whenever assigned on those endpoints and on GET /public-api/resources/partner-invites/v2.0 and GET /public-api/resources/partner-invites/v2.0/{partnerInvite}.
    7. Removed the default access policy prerequisite for options.allowAccessToPrivateChargePoints on POST /public-api/resources/partner-invites/v1.0 and PATCH /public-api/resources/partner-invites/v1.0/{partnerInvite}.
    8. Changed physicalReference uniqueness checks on POST /public-api/resources/charge-points/v2.0/{chargePoint}/evses, PATCH /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}, POST /public-api/resources/evses/v2.1, and PATCH /public-api/resources/evses/v2.1/{evse} to use the target EVSE's operator context and exclude deleted and roaming EVSEs from local reference conflicts. Roaming EVSE updates do not require local reference uniqueness.