Use the statuses endpoint to receive realtime updates of all EVSES of a CPO.

Request

The request for the statuses endpoint contains a few query parameters.

See statuses to know more about the parameters that are used with the statuses endpoint.

Response

The following is a sample response for the statuses endpoint:

{
    data: [  
      
        evses 1
          [{...},{...}],
        evses 2 
          [{...},{...}]
                
    ], 
}

Response Definitions

The following are the attributes for the statuses endpoint:

AttributeDescription
data.idThe unique id for a location. It is created by Eco-Movement, and it is stable. This attribute may change when two or more locations are merged, which results in one location only.
data.last_updatedIndicates when the location data was last updated. The date is in ISO 8601 standard and the time zone is UTC. The update could be a status update or any other update (for example, coordinates update).
data.evses.uidThe unique ID of an EVSE in the system of the CPO. It is created by the CPO and is not unique within Eco-Movement's database.
data.evses.statusIndicates if an EVSE is available for charging or not. It is the real-time status of an EVSE, which is monitored and noise-filtered by Eco-Movement. It can be one of the following:

- AVAILABLE
- BLOCKED
- CHARGING
- INOPERATIVE
- OUTOFORDER
- PLANNED
- REMOVED
- RESERVED
- UNKNOWN
data.evses.evse_idThe unique ID of an EVSE for the outside world. It is unique across all databases, but it is not always available. It is compliant with "eMI3standard version V1.0".
data.evses.last_updatedIndicates when the EVSE data was last updated. The date is in ISO 8601 standard and the time zone is UTC. The update could be a status update or any other update (for example, capabilities update).