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

3.278.0 release notes

about 5 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed request validation to reject malformed UTF-8 and characters requiring four-byte UTF-8 encoding, such as many emoji, in the following fields: name on POST /public-api/resources/electricity-meters/v1.0 and PATCH /public-api/resources/electricity-meters/v1.0/{electricityMeter}; name on POST /public-api/resources/electricity-rates/v1.0 and PUT /public-api/resources/electricity-rates/v1.0/{electricityRate}; idLabel on POST /public-api/resources/id-tags/v2.0 and PATCH /public-api/resources/id-tags/v2.0/{idTag}; description on POST /public-api/resources/installer-jobs/v1.0 and PATCH /public-api/resources/installer-jobs/v1.0/{installerJob}; name and floorLevel on POST /public-api/resources/locations/v2.0/{location}/charging-zones and PATCH /public-api/resources/locations/v2.0/{location}/charging-zones/{chargingZone}; name on POST /public-api/resources/circuits/v2.0 and PATCH /public-api/resources/circuits/v2.0/{circuit}; and name and externalId on POST /public-api/resources/partner-invite-corporate-billing-policies/v1.0 and PATCH /public-api/resources/partner-invite-corporate-billing-policies/v1.0/{corporateBillingPolicy}. Consumers must exclude these characters from the affected fields.
  2. ✨ New features
    1. Added the optional correction response property to GET /public-api/resources/partner-expenses/v1.2, GET /public-api/resources/partner-revenues/v1.2, POST /public-api/actions/partner-expense/v1.0/{partnerExpense}/set-custom-fields, and POST /public-api/actions/partner-revenue/v1.0/{partnerRevenue}/set-custom-fields. This property provides correction details when an expense or revenue record reverses or replaces another record.
    2. Added the optional totals.alreadyPaid response property to GET /public-api/resources/partner-settlement-reports/v1.1 and GET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}. Returned alongside totals.payableRevenue, it identifies revenue earned in the report's period that another report had already paid when this report was generated.
  3. 🔧 Improvements
    1. Changed PUT /public-api/resources/electricity-rates/v1.0/{electricityRate} to return 422 with validation details for invalid update data instead of a generic 500 error.
    2. Changed GET /public-api/resources/electricity-rates/v2.0/{electricityRate}/price-periods/date to populate the date field correctly for date-specific price periods while retaining newest-date-first ordering.
    3. Changed EVSE responses to omit emi3Id when a roaming EVSE has no identifier, avoiding a failed response. This applies 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}.
    4. Changed GET /public-api/resources/partner-expenses/v1.0 to use stored payment figures for totalAmount, subtotal, operatorDiscountPercentage, and operatorDiscountAmount when available. Correction records now return the reversed amount with a negative sign when the original payment figures are available, and reimbursement and revenue-sharing records use their net amount for totalAmount.