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

3.266.0 release notes

about 1 hour ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Added a 255-character limit to name, businessName, address, city, and region, and to each translation in translatedName, translatedAddress, translatedCity, and translatedRegion, on POST /public-api/resources/partners/v2.0 and PATCH /public-api/resources/partners/v2.0/{partner}. Requests exceeding these limits are rejected.
    2. Changed charge point ownership validation to reject partners and partner contracts outside the caller's accessible scope on POST /public-api/resources/charge-points/v1.0, PATCH /public-api/resources/charge-points/v1.0/{chargePoint}, POST /public-api/resources/charge-points/v2.0, and PATCH /public-api/resources/charge-points/v2.0/{chargePoint}. This applies to ownerPartnerId and ownerPartnerContractId in v1.0, and partner.id, partner.contractId, and the legacy partner.contactId in v2.0.
    3. Changed userGroupIds validation to reject groups outside the caller's operator and partner access scope on POST /public-api/resources/users/v1.0, PATCH /public-api/resources/users/v1.0/{user}, POST /public-api/resources/users/v1.1, and PATCH /public-api/resources/users/v1.1/{user}.
    4. Changed restrictions.partnerRestriction.partnerIds validation to require partners to belong to the coupon or template's operator on POST /public-api/resources/energy-coupons/v1.0, POST /public-api/resources/energy-coupon-templates/v1.0, and PATCH /public-api/resources/energy-coupon-templates/v1.0/{energyCouponTemplate}.
    5. Changed partnerId validation to reject partners outside the caller's accessible scope on POST /public-api/resources/id-tags/v2.0, PATCH /public-api/resources/id-tags/v2.0/{idTag}, and PATCH /public-api/resources/partner-invites/v1.0/{partnerInvite}.
    6. Changed email validation to prevent assigning a platform-staff email address when creating a partner administrator through POST /public-api/resources/partners/v2.0/{partner}/admins, or when updating an administrator whose current address is not a platform-staff address through PATCH /public-api/resources/partners/v2.0/{partner}/admins/{admin}.
  2. ✨ New features
    1. Added PATCH /public-api/resources/admins/v1.0/{admin} to update administrator profiles, roles, locale, IP allowlists, site-manager location assignments, and account expiration dates. Email, password, status, and organizational ownership cannot be changed through this endpoint.
    2. Added POST /public-api/actions/admin/v1.0/{admin}/activate and POST /public-api/actions/admin/v1.0/{admin}/deactivate to manage administrator account status. Successful requests return the updated administrator with status 202; transitions that conflict with the account's current state return 409.
    3. Added status, adminType, expiresOn, locale, whitelistedIps, jobTitle, department, phone, address, postCode, city, region, country, internalNotes, locationIds, signInMethods, isPasswordTwoFactorProtected, createdAt, and updatedAt to administrator responses on GET /public-api/resources/admins/v1.0 and GET /public-api/resources/admins/v1.0/{admin}. Optional fields are omitted when unavailable or not applicable.
    4. Added the experimental GET /public-api/resources/evses/v2.1/{evse}/effective-tariffs endpoint to retrieve applicable tariffs with calculated pricing, including derived prices and time-of-use energy price periods where available. Use audience=all, audience=ad_hoc, or audience=user with the corresponding operatorId or userId; this endpoint's schema and behavior may change without a version bump while experimental.
    5. Added the optional boolean reimbursement.autoAssignPoliciesEnabled to requests on POST /public-api/resources/partners/v2.0 and PATCH /public-api/resources/partners/v2.0/{partner}, and to their responses, GET /public-api/resources/partners/v2.0, GET /public-api/resources/partners/v2.0/{partner}, and POST /public-api/actions/partner/v1.0/{partner}/set-custom-fields. It defaults to false and controls automatic reimbursement-policy assignment for subsequent invite acceptances, policy assignments, and charge point ownership changes, without retroactively changing existing assignments.
    6. Added the taxCountry response property and filter[taxCountry] query filter to GET /public-api/resources/partner-expenses/v1.2 and GET /public-api/resources/partner-revenues/v1.2. Also added taxCountry to the response from POST /public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields.
    7. Added the optional filter[primaryOnly] query filter to GET /public-api/resources/locations/v2.0, GET /public-api/resources/charge-points/v2.0, GET /public-api/resources/evses/v2.1, and GET /public-api/resources/roaming-cpos/v1.0. When multi-connection roaming support is enabled, setting it to true returns only primary records rather than duplicate representations received through multiple roaming connections.
    8. Added filter[status], filter[adminType], filter[roleId], and filter[email] to GET /public-api/resources/admins/v1.0. Email matching is exact and case-insensitive, and filters combine using AND.
  3. 🔧 Improvements
    1. Expanded filter[origin] with home-charging-reimbursement and home-charging-reimbursement-fee on GET /public-api/resources/partner-expenses/v1.0, GET /public-api/resources/partner-expenses/v1.1, and GET /public-api/resources/partner-expenses/v1.2, and with home-charging-reimbursement on GET /public-api/resources/partner-revenues/v1.0 and GET /public-api/resources/partner-revenues/v1.1. The corresponding reimbursement origins can now appear in v1.1 expense and revenue responses, and both expense origins can appear in v1.2 expense responses.
    2. Changed home-charging reimbursement serialization on GET /public-api/resources/partner-expenses/v1.0 and GET /public-api/resources/partner-revenues/v1.0 to return reimbursement amounts correctly. Revenue records without a charging session omit chargingSessionId, startedAt, duration, chargePointName, and startedAtLocal, return authorization as null, and use the revenue's currency.
    3. Expanded billingStatus with dropped in responses from 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. Also added dropped as an accepted value for filter[billingStatus] on the session listing endpoint.
    4. Expanded failureReason with no_valid_authorized_token in responses from GET /public-api/resources/bookings/v1.0 and GET /public-api/resources/bookings/v1.0/{booking}.
    5. Changed PATCH /public-api/resources/transactions/v1.0/{transaction} to preserve the existing amount excluding tax when no associated purchase order is available and totalAmount remains unchanged at the currency's precision. Also preserved an existing order association when no replacement purchase order is available.
    6. Changed charge point ownership validation errors to identify the request fields consumers can correct on POST /public-api/resources/charge-points/v1.0, PATCH /public-api/resources/charge-points/v1.0/{chargePoint}, POST /public-api/resources/charge-points/v2.0, and PATCH /public-api/resources/charge-points/v2.0/{chargePoint}. Errors now use ownerPartnerId and ownerPartnerContractId in v1.0, and partner.id, partner.contractId, or the submitted legacy partner.contactId in v2.0.
    7. Changed electricity rate name validation on POST /public-api/resources/electricity-rates/v2.0 and PATCH /public-api/resources/electricity-rates/v2.0/{electricityRate} to reject unsupported four-byte Unicode characters, such as emoji, as validation errors rather than allowing a storage failure.
    8. Changed POST /public-api/resources/tariffs/v1.0/{tariff}/scheduled-changes to sanitize description and additionalInformation before storing scheduled pricing changes.