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

3.149.0 release notes

16 minutes ago by ReadMe API
  1. ✨ New features
    1. Added the optional lastNetworkStatusUpdateAt property to Charge Point responses on GET /resources/charge-points/v2.0, POST /resources/charge-points/v2.0, GET /resources/charge-points/v2.0/{chargePoint}, and PATCH /resources/charge-points/v2.0/{chargePoint}. This field contains the timestamp of the last network status change.
    2. Added the optional corporateBilling.frequency and corporateBilling.limit properties to Partner requests and responses on GET /resources/partners/v2.0, POST /resources/partners/v2.0, GET /resources/partners/v2.0/{partner}, and PATCH /resources/partners/v2.0/{partner}. These fields allow configuring billing limits with a specified frequency period (e.g., weekly, monthly) instead of fixed monthly limits.
    3. Added the optional options.corporateBillingLimit property to Partner Invite requests and responses on GET /resources/partner-invites/v1.0, POST /resources/partner-invites/v1.0, GET /resources/partner-invites/v1.0/{partnerInvite}, and PATCH /resources/partner-invites/v1.0/{partnerInvite}. This field allows setting a corporate billing spending limit for the invited user.
    4. Added the optional invoiceDetails.lastUpdatedAt property to User responses on GET /resources/users/v1.0, POST /resources/users/v1.0, GET /resources/users/v1.0/{user}, PATCH /resources/users/v1.0/{user}, GET /resources/users/v1.0/{user}/invoice-details, POST /resources/users/v1.0/{user}/invoice-details, and the v1.1 equivalents. This field contains the timestamp when the user's invoice details were last modified.
    5. Added the optional filter.invoiceDetailsLastUpdatedAfter and filter.invoiceDetailsLastUpdatedBefore query parameters to GET /resources/users/v1.0 and GET /resources/users/v1.1. These filters allow retrieving users whose invoice details were modified within a specific date range.
  2. 🔧 Improvements
    1. Made the email property conditionally optional on POST /actions/transactions/v1.0/{transaction}/issue-invoice. The field requirement now depends on the operator's invoice processor configuration—if the email field is configured as optional for the invoice type being issued, it no longer needs to be provided.
  3. 🗑️ Deprecations
    1. Deprecated the corporateBilling.monthlyLimit property on Partner endpoints (GET /resources/partners/v2.0, POST /resources/partners/v2.0, GET /resources/partners/v2.0/{partner}, PATCH /resources/partners/v2.0/{partner}). Use the new corporateBilling.frequency and corporateBilling.limit properties instead for more flexible billing period configuration.