HomeGuidesAPI ReferenceChangelog
Terms of Use
Changelog
Terms of Use
Start typing to search…
Back to All

3.162.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Notes endpoints for Charge Points, EVSEs, Locations, Partners, and Sub-operators (/resources/charge-points/v2.0/{chargePoint}/notes, /resources/evses/v2.1/{evse}/notes, /resources/locations/v2.0/{location}/notes, /resources/partners/v2.0/{partner}/notes, /resources/sub-operators/v2.0/{subOperator}/notes) now require view permission on the parent resource. Requests without this permission will receive a 403 response.
  2. ✨ New features
    1. Added new Subscription Billing Periods endpoints: GET /resources/users/v1.0/{user}/subscription-billing-periods and GET /resources/users/v1.0/{user}/subscription-billing-periods/{billingPeriod}. These return billing period details including amounts, fees, currency, payment failure information, and obligation transfer timestamps. The listing endpoint supports filtering by subscriptionPlanId, subscriptionId, date ranges (startedAfter, startedBefore, endedAfter, endedBefore), and hasUnresolvedPaymentFailure.
    2. Added the optional emi3Id property to EVSE responses on GET /resources/charge-points/v2.0/{chargePoint}/evses, POST /resources/charge-points/v2.0/{chargePoint}/evses, GET /resources/charge-points/v2.0/{chargePoint}/evses/{evse}, PATCH /resources/charge-points/v2.0/{chargePoint}/evses/{evse}, GET /resources/evses/v2.1, POST /resources/evses/v2.1, GET /resources/evses/v2.1/{evse}, and PATCH /resources/evses/v2.1/{evse}. This field contains the eMI3 identifier when available.
    3. Added the optional subscriptionBillingPeriodId and settledByTransactionId properties to Transaction responses on GET /resources/transactions/v1.0, POST /resources/transactions/v1.0, GET /resources/transactions/v1.0/{transaction}, and PATCH /resources/transactions/v1.0/{transaction}. These fields link transactions to their associated subscription billing period and settlement transaction, respectively.
    4. Added new subscriptionBillingPeriodId and settledByTransactionId filter parameters to GET /resources/transactions/v1.0 for filtering transactions by their subscription billing period or settlement transaction.
    5. Added the new corporateBilling.limitReached notification type to all Notifications endpoints (/notifications/v1.0, /notifications/v2.0, and /actions/notifications/v1.0/{notification}/resend), available in both request and response payloads.
  3. 🔧 Improvements
    1. Changed the tokenizationMethod field on Transaction responses to only derive its value from wallet type for Apple Pay and Google Pay wallets. Previously, other wallet types could produce incorrect tokenization method values.