3.155.0 release notes
about 2 hours ago by ReadMe API
- ⚠️ Breaking changes
- Changed
intervalPricingbehavior on tariff pricing responses: the API now returns only the explicitly configured time periods. Previously, gaps between configured periods were automatically filled with default-priced entries covering the full 24-hour day. Consumers relying on complete day coverage must now handle partial period lists.
- Changed
- ✨ New features
- Added new filter parameters to
GET /resources/sessions/v1.0:filter[roaming][roamingOperatorEmspIds]to filter by roaming eMSP operator IDs, andfilter[roaming][roamingConnectionIds]to filter by roaming connection IDs. - Added new filter parameters to
GET /resources/subscriptions/v1.0:filter[startedAfter]andfilter[startedBefore]to filter by subscription start date,filter[endedAfter]andfilter[endedBefore]to filter by subscription end date, andfilter[statusChangedAfter]andfilter[statusChangedBefore]to filter by the date the subscription status last changed. - Added the
filter[sessionId]parameter toGET /resources/cdrs/v2.0to filter CDRs by internal session ID. - Added
roamingas a new allowed value for thecategoryfield on Issue endpoints (POST /resources/issues/v1.0,PATCH /resources/issues/v1.0/{issue}). The same value is now also returned in Issue responses. - Added
sessionas a new allowed value for thekeyResource.resourceTypefield when creating issues viaPOST /resources/issues/v1.0. - Expanded the
keyResource.resourceTyperesponse field on Issue endpoints to include new values:roaming-cdr,roaming-connection, andsession.
- Added new filter parameters to
- 🔧 Improvements
- Reactivated the
statusfield on Location requests forPOST /resources/locations/v2.0andPATCH /resources/locations/v2.0/{location}, allowing location status to be set during creation and updates.
- Reactivated the