Outgoing data

In addition to the ingoing REST API there is a outgoing stream of events from the system.

You can use these events to monitor status, progress etc. of charging sessions, charge points and so on.

Charge points

In this stream all events related to the state of a charge point are sent.

Notice that the concept of a charge point do not exists in either OCPI or OICP. In the case of roaming always look at locations.

Link to model: https://developers.bloom-charge.com/reference#model/chargepoint

Locations

In this stream all events related to the state of a location are sent.

Status changes of the individual connectors on the location are published in a separate stream.

Link to the model: https://developers.bloom-charge.com/reference#model/location

EVSE status

State changes of all EVSE (connectors on charge points).

The model being published in this stream looks like this:

public class EvseStatusMessage
{
    public Origin Origin { get; set; }

    public string LocationId { get; set; }

    public string? Geohash { get; set; }

    public string EvseId { get; set; }

    public string? ChargePointId { get; set; }

    public EvseStatusValue Status { get; set; }

    public IReadOnlyList<EvseConnectorStatus> Connectors { get; set; }
}

public class EvseConnectorStatus
{
    public int ConnectorId { get; set; }

    public ConnectorStatus? Status { get; set; }
}

Link to ConnectorStatus : https://docs.scalar.com/editor#/reference/model/connectorstatus

Identities

Link to the model: https://developers.bloom-charge.com/reference#model/RfidCard

Sessions

All session related events are streamed as they happen with minimal delay. This apply to all types of session regardless of the protocol OCPP, OCPI and OICP.