EVerest API definition for session cost consumer 1.0.0

API for EVerest API clients that consume session cost and tariff information from the session_cost interface. See the Integrate Tariff and Cost how-to guide for OCPP-specific configuration and message flow details.

  • #EVerest
  • #SessionCost

Servers

  • mqtt://localhost:1883/everest_api/1/session_cost_consumer/{module_id}mqttdefault

    default local MQTT

    object
    module_id
    required
    string

    The ID of the module as defined in the EVerest config file.

Operations

  • RECEIVE e2m/tariff_message

    Published at authorization time and whenever the CSMS sends updated pricing during a session. Contains human-readable price text in one or more languages.

    Operation IDreceive_tariff_message

    Available only on servers:

    Accepts the following message:

    Receive tariff messagetariff_message

    Tariff and pricing information for a charging session

    Message IDtariff_message
    object

    Message containing cost information

    Examples

  • RECEIVE e2m/session_cost

    Published periodically during a session and once when it ends. Contains session cost broken down into chunks, current and upcoming pricing, and optional display messages.

    Operation IDreceive_session_cost

    Available only on servers:

    Accepts the following message:

    Receive session costsession_cost

    Running or final cost of a charging session

    Message IDsession_cost
    object

    Session cost object containing the total cost of the session and a list of chunks

    Examples

  • RECEIVE e2m/heartbeat

    Operation IDreceive_heartbeat

    Available only on servers:

    Accepts the following message:

    Receive heartbeatreceive_heartbeat

    Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration

    Message IDreceive_heartbeat
    Payload
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached

    Examples

  • SEND m2e/communication_check

    Operation IDsend_communication_check

    Available only on servers:

    Accepts the following message:

    Send communication checksend_communication_check

    Signal to EVerest that communication is good or check shall be stopped

    Message IDsend_communication_check
    Payload
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

    Examples

Messages

  • #1Receive tariff messagereceive_tariff_message

    Tariff and pricing information for a charging session

    Message IDreceive_tariff_message
    object

    Message containing cost information

  • #2Receive session costreceive_session_cost

    Running or final cost of a charging session

    Message IDreceive_session_cost
    object

    Session cost object containing the total cost of the session and a list of chunks

  • #3Receive heartbeatreceive_heartbeat

    Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration

    Message IDreceive_heartbeat
    Payload
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached

  • #4Send communication checksend_communication_check

    Signal to EVerest that communication is good or check shall be stopped

    Message IDsend_communication_check
    Payload
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

Schemas

  • CommunicationCheck
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

  • HeartBeatId
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached