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

3.255.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed non-empty filter[customFields.*] values that refer to unknown, unavailable, or non-filterable fields to return a 400 error instead of being ignored on GET /public-api/resources/partners/v2.0, GET /public-api/resources/partner-settlement-reports/v1.0, GET /public-api/resources/payment-terminals/v1.1, GET /public-api/resources/sessions/v1.0, GET /public-api/resources/reimbursement-records/v1.0, and GET /public-api/resources/reimbursement-reports/v1.0.
  2. ✨ New features
    1. Added optional pricing.connectionFeeMaximumSessionDuration (minutes) and pricing.connectionFeeMaximumSessionEnergy (kWh) fields to tariff create and update requests and scheduled-change create and update requests: POST /public-api/resources/tariffs/v1.0, PUT /public-api/resources/tariffs/v1.0/{tariff}, PATCH /public-api/resources/tariffs/v1.0/{tariff}, POST /public-api/resources/tariffs/v1.0/{tariff}/scheduled-changes, and PATCH /public-api/resources/tariffs/v1.0/{tariff}/scheduled-changes/{scheduledChange}; when configured, the connection fee is not charged after the corresponding session duration or energy limit is exceeded. The fields are also returned by these endpoints and by GET /public-api/resources/tariffs/v1.0, GET /public-api/resources/tariffs/v1.0/{tariff}, GET /public-api/resources/tariff-snapshots/v1.0/{tariffSnapshot}, GET /public-api/resources/tariffs/v1.0/{tariff}/scheduled-changes, and GET /public-api/resources/tariffs/v1.0/{tariff}/scheduled-changes/{scheduledChange}.
  3. 🔧 Improvements
    1. Expanded the status values on GET /public-api/resources/bookings/v1.0 and GET /public-api/resources/bookings/v1.0/{booking} to include pending and rejected; the listing endpoint also accepts these values in filter[status].
    2. Expanded network.protocol to accept ocpp 1.5 json when creating or updating charge points through POST /public-api/resources/charge-points/v2.0 and PATCH /public-api/resources/charge-points/v2.0/{chargePoint}. The value can also appear in responses from these endpoints and GET /public-api/resources/charge-points/v2.0 and GET /public-api/resources/charge-points/v2.0/{chargePoint}.
    3. Expanded language on partner invites and notifications.billing.settlementReportLanguage on partners to support fa (Persian) and ur (Urdu) in requests and responses. Affected endpoints are GET /public-api/resources/partner-invites/v2.0, POST /public-api/resources/partner-invites/v2.0, GET /public-api/resources/partner-invites/v2.0/{partnerInvite}, PATCH /public-api/resources/partner-invites/v2.0/{partnerInvite}, GET /public-api/resources/partners/v2.0, POST /public-api/resources/partners/v2.0, GET /public-api/resources/partners/v2.0/{partner}, PATCH /public-api/resources/partners/v2.0/{partner}, and POST /public-api/actions/partner/v1.0/{partner}/set-custom-fields.