As part of our ongoing effort to integrate cloud-connected assets with the company-wide asset registry, we are initiating a new migration process.
This includes the deprecation of temporary endpoints and events originally created to facilitate the migration from Enode.
Legacy/Migration
These legacy endpoints are no longer documented and should not be used. Please transition to the new standard endpoint immediately to ensure full, supported access to your account’s assets.
Endpoint
These endpoints were originally designed to mimic Enode models to facilitate the migration path. They are now being deprecated in favor of the standard GridX-wide asset model.
/systems/{systemID}/vehicles/systems/{systemID}/vehicles/{vehicleID}/systems/{systemID}/vehicles/link/systems/{systemID}/vehicles/control/systems/{systemID}/vehicles/start-boost/systems/{systemID}/vehicles/stop-boost
Events
The deprecated events functioned as direct pass-throughs of the raw Enode payload. These have been superseded by granular event topics (such as appliance/delete or ev/measurement) and should no longer be used.
/ev/create/ev/update/ev/delete
Current API deprecation
We have updated the new API to better align with our internal asset models. Please note that this includes small structural changes to the EV object.
EV object
tags.[0].year: is deprecated in favor of theyearfield in the root object.updateAt: is deprecated in favor ofupdatedAt.
Deadline
As part of the migration to the GridX-wide asset model, we are deprecating the Enode migration path.
Effective January 28th, the legacy Enode like endpoints and events will be fully deprecated. Please ensure you have transitioned to the new standard endpoints (such as .../{assetID}/control) before this date.