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

3.254.0 release notes

about 3 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed the success status of POST /public-api/actions/reimbursement-record/v1.0/{reimbursementRecord}/issue-credit from 201 to 202. The response still contains the credited record in data; clients checking for 201 must accept 202 instead.
  2. ✨ New features
    1. Added POST /public-api/actions/reimbursement-record/v1.0/{reimbursementRecord}/set-custom-fields and POST /public-api/actions/reimbursement-report/v1.0/{reimbursementReport}/set-custom-fields to update custom field values without changing reimbursement amounts. Send a customFields object; omitted fields remain unchanged and null clears a value. These endpoints are experimental.
    2. Added the optional customFields response property to GET /public-api/resources/reimbursement-records/v1.0, GET /public-api/resources/reimbursement-records/v1.0/{reimbursementRecord}, GET /public-api/resources/reimbursement-reports/v1.0, and GET /public-api/resources/reimbursement-reports/v1.0/{reimbursementReport} when applicable custom field values are available.
    3. Added custom field filtering to GET /public-api/resources/reimbursement-records/v1.0 and GET /public-api/resources/reimbursement-reports/v1.0. Use filter[customFields.<identifier>] for a configured, filterable field; range filters accept from and to bounds.
    4. Added the optional reason property to POST /public-api/actions/session/v1.0/{session}/change-tariff to record why the tariff was changed.
    5. Added POST /public-api/actions/session/v1.0/{session}/resume-billing to complete suspended billing using the required type value bill_as_is or free_session, with an optional reason.
    6. Added POST /public-api/actions/session/v1.0/{session}/expedite-billing to run billing validation for a finished session still awaiting it, with an optional reason.
    7. Added POST /public-api/actions/session/v1.0/{session}/recalculate to queue recalculation of a session's charging periods and amounts, with an optional reason. A 202 response means the work was queued, not that recalculation has finished.
    8. Added POST /public-api/actions/users/v1.0/{user}/terminate-subscription to permanently terminate a user's active subscription. The request requires a reason; termination is rejected if the subscription cannot be terminated in its current state.
  3. 🔧 Improvements
    1. Expanded the accepted connector type and booking evseCriteria.connectorType values to include nema-10-30, nema-10-50, nema-14-30, and nema-14-50. These values can also appear in connector, EVSE, charge point, and booking responses.
    2. Expanded the supported language values for partner invites and notifications.billing.settlementReportLanguage for partners to include be, bn, hy, mt, and sw. These values may also appear in the corresponding responses.
    3. Expanded the status values returned by GET /public-api/resources/subscriptions/v1.0 and GET /public-api/resources/subscriptions/v1.0/{subscription} to include terminated.
    4. Changed custom field filters on GET /public-api/resources/payment-terminals/v1.1, GET /public-api/resources/partners/v2.0, GET /public-api/resources/partner-settlement-reports/v1.0, and GET /public-api/resources/sessions/v1.0 so unknown, disabled, or non-filterable custom field criteria are ignored rather than causing an error. Other valid filters still apply.
    5. Made null acceptable for existing filters on GET /public-api/resources/reimbursement-records/v1.0 and GET /public-api/resources/reimbursement-reports/v1.0; empty date and report criteria no longer restrict results.
  4. 🗑️ Deprecations
    1. Deprecated the include query parameter on GET /public-api/resources/issues/v1.0/{issue}.