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

3.264.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Made userId optional in create-type booking request responses from GET /public-api/resources/booking-requests/v1.0, POST /public-api/resources/booking-requests/v1.0, and GET /public-api/resources/booking-requests/v1.0/{bookingRequest}. Consumers must handle its omission when no local user is associated with the request; userId remains required when submitting a create-type request.
    2. Changed partnerId validation on PATCH /public-api/resources/partner-invites/v1.0/{partnerInvite} to reject partners outside the API token's operator when the token is operator-scoped.
    3. Changed booking listing visibility on GET /public-api/resources/bookings/v1.0 to require booking read permission and bookings to be enabled in the requesting operator context, while applying operator and partner access restrictions. Requests without the required visibility return no bookings.
  2. ✨ New features
    1. Added the booking_changed notification type for subscriptions through POST /public-api/notifications/v2.0 and PUT /public-api/notifications/v2.0/{notification}, and for resending failed notifications through POST /public-api/actions/notifications/v1.0/{notification}/resend. Booking change callbacks include notification, action, bookingId, status, lastUpdatedAt, and an optional failureReason.
    2. Added an optional error object to the 200 response from POST /public-api/actions/charge-point/v1.0/{chargePoint}/send-custom-ocpp when the charge point returns an OCPP call error. The object contains code, description, and details.
    3. Added the optional taxBreakdown response field to GET /public-api/resources/partner-revenues/v1.2, GET /public-api/resources/partner-expenses/v1.2, and POST /public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields. It splits the revenue's partner share or the expense's total amount by tax rate, with taxPercentage and amount.withoutTax / amount.withTax for each entry, and is omitted when no breakdown was recorded.
  3. 🔧 Improvements
    1. Expanded the notifications response values to include booking_changed on GET /public-api/notifications/v2.0, POST /public-api/notifications/v2.0, GET /public-api/notifications/v2.0/{notification}, and PUT /public-api/notifications/v2.0/{notification}. Expanded the same field to include booking_changed, cdr.processed, CoOperatorInsightChangedNotification, and SignedFirmwareStatusNotification on GET /public-api/notifications/v1.0, POST /public-api/notifications/v1.0, GET /public-api/notifications/v1.0/{notification}, and PUT /public-api/notifications/v1.0/{notification}.
    2. Changed ocpiData.totalEnergy in responses from GET /public-api/resources/cdrs/v2.0 and GET /public-api/resources/cdrs/v2.0/{cdr} to use the recorded energy value in kWh.
    3. Changed booking detail visibility on GET /public-api/resources/bookings/v1.0/{booking} to allow operator-scoped access through either the booking's user or its location, subject to booking read permission and applicable partner and installation-company restrictions.