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

3.206.0 release notes

about 3 hours ago by ReadMe API
  1. ✨ New features
    1. Added the optional filter[operatorId] query filter to GET /public-api/resources/sub-operators/v2.0, so you can now narrow sub-operator listings to a specific operator.
    2. Added the optional operatorId response property to sub-operator payloads returned by GET /public-api/resources/sub-operators/v2.0, POST /public-api/resources/sub-operators/v2.0, GET /public-api/resources/sub-operators/v2.0/{subOperator}, and PATCH /public-api/resources/sub-operators/v2.0/{subOperator}.
  2. 🔧 Improvements
    1. Made POST /public-api/resources/energy-coupons/v1.0 honor restrictions.evseType when creating an energy coupon, so the EVSE type restriction is now applied from the nested restrictions object even when the legacy top-level evseType field is omitted.
    2. Changed partnerName to use a more reliable canonical fallback on GET /public-api/resources/partner-expenses/v1.0, GET /public-api/resources/partner-expenses/v1.1, GET /public-api/resources/partner-expenses/v1.2, GET /public-api/resources/partner-revenues/v1.0, GET /public-api/resources/partner-revenues/v1.1, and GET /public-api/resources/partner-revenues/v1.2, reducing cases where partner names could be incomplete or inconsistent across locales.
  3. 🗑️ Deprecations
    1. Deprecated the top-level evseType field on POST /public-api/resources/energy-coupons/v1.0. Use restrictions.evseType instead.
    2. Deprecated the evseType response field on POST /public-api/resources/energy-coupons/v1.0, GET /public-api/resources/energy-coupons/v1.0/{energyCoupon}, GET /public-api/resources/energy-coupons/v1.0, and POST /public-api/actions/energy-coupon/v1.0/redeem-code.