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

3.200.0 release notes

about 2 hours ago by ReadMe API
  1. ⚠️ Breaking changes
    1. Changed the allowed include values on GET /public-api/resources/sessions/v1.0. The endpoint now accepts only externalAppData; requests that previously sent other include values are now rejected.
  2. ✨ New features
    1. Added vehicle management endpoints: GET /public-api/resources/vehicles/v1.0, POST /public-api/resources/vehicles/v1.0, GET /public-api/resources/vehicles/v1.0/{vehicle}, PATCH /public-api/resources/vehicles/v1.0/{vehicle}, and DELETE /public-api/resources/vehicles/v1.0/{vehicle}. These endpoints let consumers list, create, read, update, and delete vehicles.
    2. Added vehicle-to-user relation endpoints: GET /public-api/resources/vehicles/v1.0/{vehicle}/relations/users, POST /public-api/resources/vehicles/v1.0/{vehicle}/relations/users, PUT /public-api/resources/vehicles/v1.0/{vehicle}/relations/users, and DELETE /public-api/resources/vehicles/v1.0/{vehicle}/relations/users/{user}. These endpoints let consumers view, attach, replace, and detach vehicle-user assignments.
    3. Added the optional vehicleId field to Id tag payloads on POST /public-api/resources/id-tags/v2.0 and PATCH /public-api/resources/id-tags/v2.0/{idTag}, and added vehicleId to responses from GET /public-api/resources/id-tags/v2.0, GET /public-api/resources/id-tags/v2.0/{idTag}, POST /public-api/resources/id-tags/v2.0, and PATCH /public-api/resources/id-tags/v2.0/{idTag}. This lets consumers link an Id tag to a vehicle.
    4. Added support for filtering Id tags by vehicleId on GET /public-api/resources/id-tags/v2.0.
    5. Added the optional vehicleId field to session responses on GET /public-api/resources/sessions/v1.0 and GET /public-api/resources/sessions/v1.0/{session}.
    6. Added support for include[]=vehicle on GET /public-api/resources/sessions/v1.0/{session}. When requested, the response now includes a vehicle object with the linked vehicle details and verification status.
  3. 🔧 Improvements
    1. Expanded the type enum in Id tag responses on POST /public-api/resources/id-tags/v2.0 and PATCH /public-api/resources/id-tags/v2.0/{idTag} to include emaid.
    2. Expanded the protocol enum in roaming connection responses on GET /public-api/resources/roaming-connections/v2.0 and GET /public-api/resources/roaming-connections/v2.0/{roamingConnection} to include ocpi_e_clearing_2_1_1.
    3. Added validation for vehicle assignments on Id tag create and update requests. When vehicleId and userId are sent together on POST /public-api/resources/id-tags/v2.0 or PATCH /public-api/resources/id-tags/v2.0/{idTag}, the API now rejects combinations where the vehicle is not available to the caller or is not linked to that user.
    4. Added validation rules on vehicle create and update requests so vin must be unique per operator, usageType is restricted to supported values, and operatorId is required for global administrators when creating a vehicle.