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

3.198.0 release notes

about 3 hours ago by ReadMe API
  1. ✨ New features
    1. Added support for roaming-referenced discount tariffs on POST /public-api/resources/tariffs/v1.0, PUT /public-api/resources/tariffs/v1.0/{tariff}, PATCH /public-api/resources/tariffs/v1.0/{tariff}, GET /public-api/resources/tariffs/v1.0, GET /public-api/resources/tariffs/v1.0/{tariff}, and GET /public-api/resources/tariff-snapshots/v1.0/{tariffSnapshot}. The discountTariffSettings.discountReferenceType field now accepts roaming_tariff, and roaming-based discount tariffs use the new discountType and discountValue fields in requests and responses.
    2. Added the options.settlementReportBreakdown field to the Partner v2 request and response bodies on POST /public-api/resources/partners/v2.0, PATCH /public-api/resources/partners/v2.0/{partner}, GET /public-api/resources/partners/v2.0, and GET /public-api/resources/partners/v2.0/{partner}.
    3. Added the notifications.billing.settlementReportLanguage field to the Partner v2 request and response bodies on POST /public-api/resources/partners/v2.0, PATCH /public-api/resources/partners/v2.0/{partner}, GET /public-api/resources/partners/v2.0, and GET /public-api/resources/partners/v2.0/{partner}.
  2. 🔧 Improvements
    1. Changed Public API location responses so isRoaming is now evaluated relative to the requesting token in global-access scenarios, instead of comparing against the tenant default operator. This makes GET /public-api/resources/locations and related location responses more consistent for global tokens.
    2. Changed receipt responses so totalAmount now prefers the precise stored total when available and falls back to the legacy stored total only when needed. This reduces rounding artifacts and improves compatibility with older receipts.
    3. Changed payment terminal responses so translated welcome-message values now combine terminal-specific translations with integration defaults instead of replacing the full set. This preserves default translations while still allowing per-terminal overrides.
    4. Changed OICP data in CDR responses so operatorId can now be derived from the EVSE identifier when the upstream payload omits OperatorID explicitly. This improves completeness of roaming session data returned by the API.