3.181.0 release notes
about 5 hours ago by ReadMe API
- ✨ New features
- Added
GET /public-api/resources/roaming-cpos/v1.0,GET /public-api/resources/roaming-cpos/v1.0/{roamingCpo}, andPATCH /public-api/resources/roaming-cpos/v1.0/{roamingCpo}for listing, reading, and updating remote roaming CPOs. Responses includeid,hubjectId,businessName,connectionId,enabled,countryCode,partyId,lastUpdatedAt, and a nestedcpoSettingsobject (cpoQrCodePrefix,tariffMappingMode,treatEvseStatusUnknownAs,applyCustomTariffsToEvsesWithRoamingTariff,sendsPeriodicMeterUpdates,externalTariffIntegration,phaseAcPowerFormula). - Added
GET /public-api/resources/roaming-emsps/v1.0,POST /public-api/resources/roaming-emsps/v1.0,GET /public-api/resources/roaming-emsps/v1.0/{roamingEmsp},PATCH /public-api/resources/roaming-emsps/v1.0/{roamingEmsp}, andDELETE /public-api/resources/roaming-emsps/v1.0/{roamingEmsp}for managing remote roaming EMSPs. The listing endpoint supportscountryCode,partyId, andconnectionIdfilters. Responses includeid,hubjectId,businessName,connectionId,countryCode,partyId, andlastUpdatedAt. Create/update requests requireconnectionId;countryCodeandpartyIdbecome required when the linked roaming connection has no OCPI credentials configured. - Added
GET /public-api/resources/roaming-emsps/v1.0/{roamingEmsp}/partnersfor listing the operator-to-partner assignments configured against a roaming EMSP. Supports anoperatorIdexact-match filter. Each item returnsoperatorId,partnerId, andlastUpdatedAt. - Added
POST /public-api/actions/roaming-emsp/v1.0/{roamingEmsp}/assign-partnerfor assigning (or clearing) the partner linked to a roaming EMSP for a given operator. The request body accepts an optionaloperatorId(required for global admins; must match the caller's operator for operator-scoped admins) and a requiredpartnerId(nullable to clear the assignment). - Added the
partnerId,titleContains,autoRenewal,startDateAfter,endDateBefore, andexternalIdfilters onGET /public-api/resources/partner-contracts/v1.0.
- Added
- 🔧 Improvements
- Changed the persistent-template conflict check on the apply-configuration-template action so it only runs when the request sets
shouldPersisttotrue. Non-persistent applications no longer return422 Unprocessable Entitydue to unrelated charge points already having a persistent template assigned.
- Changed the persistent-template conflict check on the apply-configuration-template action so it only runs when the request sets
- 🗑️ Deprecations
- Deprecated
GET /public-api/resources/roaming-operators/v2.0,GET /public-api/resources/roaming-operators/v2.0/{roamingOperator}, andPATCH /public-api/resources/roaming-operators/v2.0/{roamingOperator}. Use the new/public-api/resources/roaming-cpos/v1.0endpoints instead. - Deprecated
GET /public-api/resources/roaming-providers/v2.0,POST /public-api/resources/roaming-providers/v2.0,GET /public-api/resources/roaming-providers/v2.0/{roamingProvider},PATCH /public-api/resources/roaming-providers/v2.0/{roamingProvider}, andDELETE /public-api/resources/roaming-providers/v2.0/{roamingProvider}. Use the new/public-api/resources/roaming-emsps/v1.0endpoints instead.
- Deprecated