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

3.272.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed validation of partnerId updates on PATCH /public-api/resources/partner-invites/v1.0/{partnerInvite} and PATCH /public-api/resources/partner-invites/v2.0/{partnerInvite} to reject moving an invite to a partner that already has another invite with the same email address. These requests now return 422 with an email validation error.
  2. ✨ New features
    1. Added the experimental POST /public-api/actions/evse/v1.0/{evse}/set-custom-fields endpoint to update EVSE custom field values using a customFields object; omitted identifiers remain unchanged, and null clears a value. Successful requests return 202 with the updated EVSE; the endpoint's contract may change without a version bump while experimental.
    2. Added the optional customFields response object to GET and POST /public-api/resources/evses/v2.1, GET and PATCH /public-api/resources/evses/v2.1/{evse}, GET and POST /public-api/resources/charge-points/v2.0/{chargePoint}/evses, and GET and PATCH /public-api/resources/charge-points/v2.0/{chargePoint}/evses/{evse}. The object contains applicable custom field values visible to the caller and is omitted when no values are available.
    3. Added custom field filtering on GET /public-api/resources/evses/v2.1 using filter[customFields.{identifier}] for enabled, visible custom fields that support filtering. Unavailable or unsupported field identifiers return 400, while invalid filter values return 422.
  3. 🔧 Improvements
    1. Changed ordering on GET /public-api/resources/consent-history/v1.0 to use descending record ID as a tie-breaker when creation timestamps match, making cursor pagination deterministic for those records.