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

3.259.0 release notes

about 5 hours ago by ReadMe API
  1. ✨ New features
    1. Added the optional averagePrice request and response field to GET and POST /public-api/resources/locations/v2.0 and GET and PATCH /public-api/resources/locations/v2.0/{location}. Prices use the location operator's currency and unit-price precision; 0 indicates free charging, null on PATCH clears the price, and the response omits the field when no price is set.
    2. Added the optional userId request field to POST /public-api/actions/locations/v2.0/{location}/check-booking-availability to check availability for a specific driver. The user must be visible to the requesting administrator; unknown or inaccessible users and null values are rejected.
    3. Added the optional monthlyPlatformFees.perPrivateEvseOfOtherPartners and revenueSharing.partnerSharePercentagePrivateEvseAccessFees fields to requests and responses on GET and POST /public-api/resources/partner-contracts/v1.0 and GET, PATCH, and PUT /public-api/resources/partner-contracts/v1.0/{partnerContract}. These configure a non-negative, tax-exclusive access fee per private EVSE of other partners and a revenue share from private EVSE access fees between 0 and 100 percent; on updates, null clears a value and omission preserves it.
    4. Added GET /public-api/resources/partner-settlement-reports/v1.1 and GET /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport} with a totals object replacing the flat total fields used in v1.0. Each total contains withoutTax and, when stored, withTax.
    5. Added settlement record endpoints in v1.1: GET and POST /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records, and GET, PUT, and DELETE /public-api/resources/partner-settlement-reports/v1.1/{partnerSettlementReport}/records/{partnerSettlementRecord}.
    6. Added support for include[]=reimbursementRecords on GET /public-api/resources/sessions/v1.0/{session}. The response includes reimbursementRecords ordered by record ID when the caller has permission to view them, returns an empty array when none exist, and otherwise omits the field.
  2. 🔧 Improvements
    1. Expanded the errorCode and rejectedPaymentMethodErrorCode values in 202 responses from POST /public-api/actions/charge-point/v1.0/{chargePoint}/start/{evse} and POST /public-api/actions/evse/v1.0/{evse}/start to include corporate_billing_disabled. The same value is now supported in failureReason responses from GET /public-api/resources/ocpi-commands/v1.0 and GET /public-api/resources/ocpi-commands/v1.0/{ocpiCommand}, and in the listing's filter[failureReason] parameter.
    2. Expanded the failureReason response values on GET /public-api/resources/bookings/v1.0 and GET /public-api/resources/bookings/v1.0/{booking} to include user_no_longer_has_access.
    3. Changed POST /public-api/actions/configuration-template/v1.0/{template}/apply-to-charge-points to replace existing persistent configuration templates when applying a persistent template, instead of rejecting the request with 422 because of a persistent-template conflict.
    4. Changed Valina updates on PATCH /public-api/resources/payment-terminals/v1.1/{paymentTerminal} to preserve screensaverWelcomeMessage and screensaverPaymentMethods when those fields are omitted from the request.
    5. Changed discount tariff responses from GET /public-api/resources/tariff-snapshots/v1.0/{tariffSnapshot} to return the stored snapshot pricing rather than pricing derived from the current referenced tariff.
  3. 🗑️ Deprecations
    1. Deprecated GET /public-api/resources/partner-settlement-reports/v1.0 and GET /public-api/resources/partner-settlement-reports/v1.0/{partnerSettlementReport}. Use the corresponding v1.1 endpoints and their totals response structure instead.
    2. Deprecated GET and POST /public-api/resources/partner-settlement-reports/v1.0/{partnerSettlementReport}/records, and GET, PUT, and DELETE /public-api/resources/partner-settlement-reports/v1.0/{partnerSettlementReport}/records/{PartnerSettlementRecord}. Use the corresponding v1.1 settlement record endpoints instead.