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

3.211.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Removed the idTags property from the request body of PATCH /public-api/resources/provisioning-certificates/v2.0/{provisioningCertificate}. Consumers can no longer update provisioning certificate ID tags through this endpoint.
    2. Expanded the notification event enum with partnerInviteCorporateBillingPolicy.changed on GET /public-api/notifications/v1.0, POST /public-api/notifications/v1.0, GET /public-api/notifications/v1.0/{notification}, PUT /public-api/notifications/v1.0/{notification}, GET /public-api/notifications/v2.0, POST /public-api/notifications/v2.0, GET /public-api/notifications/v2.0/{notification}, and PUT /public-api/notifications/v2.0/{notification}. Clients that validate notification event values against a fixed allowlist must add the new value.
  2. ✨ New features
    1. Added a new experimental Partner invite corporate billing policy resource with listing, create, read, update, delete, snapshot listing, and snapshot read endpoints under /public-api/resources/partner-invite-corporate-billing-policies/v1.0. These endpoints let consumers manage partner invite corporate billing rules including restrictions, tariff thresholds, overall cost caps, charger-type configuration, and snapshot history.
    2. Added experimental enable and disable actions for Partner invite corporate billing policies on POST /public-api/actions/partner-invite-corporate-billing-policy/v1.0/{corporateBillingPolicy}/enable and POST /public-api/actions/partner-invite-corporate-billing-policy/v1.0/{corporateBillingPolicy}/disable. Both actions return 202 Accepted and may return 409 Conflict when the requested state change cannot be applied.
    3. Added vehicle telemetry reading endpoints on GET /public-api/resources/vehicles/v1.0/telemetry-readings, GET /public-api/resources/vehicles/v1.0/{vehicle}/telemetry-readings, POST /public-api/resources/vehicles/v1.0/{vehicle}/telemetry-readings, and DELETE /public-api/resources/vehicles/v1.0/{vehicle}/telemetry-readings/{vehicleTelemetryReading}. Consumers can now list, create, and delete per-vehicle telemetry readings, including odometer data and submission timestamps.
    4. Added the optional telemetry object to responses from GET /public-api/resources/vehicles/v1.0/{vehicle} when vehicle telemetry is enabled for the operator. The new object exposes lastOdometerKm and lastOdometerAt for the most recent odometer reading.
    5. Added the optional defaultPaymentOption property to POST /public-api/actions/provisioning-certificate/v1.0/{provisioningCertificate}/issue-emaid. When both defaultPaymentOption and paymentMethod are sent, defaultPaymentOption takes precedence.
    6. Added defaultPaymentOption to provisioning certificate ID tag objects returned by GET /public-api/resources/provisioning-certificates/v2.0, POST /public-api/resources/provisioning-certificates/v2.0, GET /public-api/resources/provisioning-certificates/v2.0/{provisioningCertificate}, and PATCH /public-api/resources/provisioning-certificates/v2.0/{provisioningCertificate}. Returned idTags are now documented as present only when the certificate has at least one active ID tag.
  3. 🔧 Improvements
    1. Added new filters to GET /public-api/resources/partner-invite-corporate-billing-policies/v1.0: filter.partnerId, filter.isActive, and filter.coverageType. Consumers can now narrow policy listings without client-side filtering.
    2. Added new filters to GET /public-api/resources/vehicles/v1.0/telemetry-readings and GET /public-api/resources/vehicles/v1.0/{vehicle}/telemetry-readings: filter.source, filter.submittedAfter, and filter.submittedBefore, plus filter.vehicleId and filter.partnerId on the collection endpoint. This makes it easier to retrieve only the telemetry readings relevant to a specific time window, source, vehicle, or partner.
    3. Changed POST /public-api/actions/provisioning-certificate/v1.0/{provisioningCertificate}/issue-emaid so that if both defaultPaymentOption and paymentMethod are omitted, the issued EMAID defaults to auto. This makes the request body more forgiving for clients that rely on automatic payment selection.
  4. 🗑️ Deprecations
    1. Deprecated the paymentMethod request property on POST /public-api/actions/provisioning-certificate/v1.0/{provisioningCertificate}/issue-emaid. Consumers should migrate to defaultPaymentOption.