EVerest API definition for auth consumer 1.0.0

API to allow EVerest API clients to use the Auth module.

  • #EVerest
  • #Auth

Servers

  • mqtt://localhost:1883/everest_api/1/auth_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

  • REQUEST m2e/withdraw_authorization

    If only the evse_id is given, the granted authorization for this EVSE will be withdrawn. If only the id_token is given, the granted authorization for every EVSE where this id_token is placed will be withdrawn. If both parameters are given, the granted authorization for the given EVSE will be withdrawn, if the placed id_token matches the given id_token If no parameter is given, all granted authorizations for all EVSEs will be removed

    Operation IDsend_request_withdraw_authorization

    Available only on servers:

    Accepts the following message:

    Withdraw granted authorizationsend_request_withdraw_authorization

    Withdraw granted authorization.

    Message IDsend_request_withdraw_authorization
    object

    Examples

    REPLY INFORMATION

    REPLY CHANNEL INFORMATION

    Reply will be directed to the address specified at this location: $message.header#/replyTo

    REPLY address information

    REPLY will be sent to the address provided in:$message.header#/replyTo
  • RECEIVE

    Operation IDreceive_reply_withdraw_authorization

    Available only on servers:

    Accepts the following message:

    Reply to request to withdraw authorizationreceive_reply_withdraw_authorization

    Reply to request to withdraw authorization.

    Message IDreceive_reply_withdraw_authorization
    Payload
    string

    The result of a WithdrawAuthorizationRequest: Accepted in case requested authorization was removed AuthorizationNotFound in case no match for request was found EvseNotFound in case no match for evse_id was found Rejected in case module could not process the request for other reasons

      Allowed values:
    • "Accepted"
    • "AuthorizationNotFound"
    • "EvseNotFound"
    • "Rejected"

    Examples

  • RECEIVE e2m/token_validation_status

    Direction: EVerest to Module

    Operation IDreceive_token_validation_status

    Available only on servers:

    Accepts the following message:

    Receive token validation status messagereceive_token_validation_status

    Token validation status

    Message IDreceive_token_validation_status
    object

    The token validation status

    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

  • #1Withdraw granted authorizationsend_request_withdraw_authorization

    Withdraw granted authorization.

    Message IDsend_request_withdraw_authorization
    object
  • #2Reply to request to withdraw authorizationreceive_reply_withdraw_authorization

    Reply to request to withdraw authorization.

    Message IDreceive_reply_withdraw_authorization
    Payload
    string

    The result of a WithdrawAuthorizationRequest: Accepted in case requested authorization was removed AuthorizationNotFound in case no match for request was found EvseNotFound in case no match for evse_id was found Rejected in case module could not process the request for other reasons

      Allowed values:
    • "Accepted"
    • "AuthorizationNotFound"
    • "EvseNotFound"
    • "Rejected"
  • #3Receive token validation status messagereceive_token_validation_status

    Token validation status

    Message IDreceive_token_validation_status
    object

    The token validation status

  • #4Receive 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

  • #5Send 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

  • AuthorizationType
    string

    Type of authorization of the provided token. The value of AuthorizationType can influence the authorization process

      Allowed values:
    • "OCPP"
    • "RFID"
    • "Autocharge"
    • "PlugAndCharge"
    • "BankCard"
  • object

    Contains the certificate information

  • object

    Type for a custom id token with a free-form type

  • object

    Type for an id token

  • IdTokenType
    string

    IdTokenType of the provided token. Required by OCPP2.0.1 to distinguish between different types of tokens.

      Allowed values:
    • "Central"
    • "eMAID"
    • "MacAddress"
    • "ISO14443"
    • "ISO15693"
    • "KeyCode"
    • "Local"
    • "NoAuthorization"
  • object

    Type for IdToken provided by auth token providers. Contains additional information about the IdToken like the source and purpose

  • TokenValidationStatus
    string

    Ongoing token validation status

    • TimedOut Occurs when the token has been authorized but no connector is selected within connection_timeout seconds
      Allowed values:
    • "Processing"
    • "Accepted"
    • "Rejected"
    • "TimedOut"
  • object

    The token validation status

  • object

    Request to withdraw granted authorization. If only the evse_id is given, the granted authorization for this EVSE will be withdrawn. If only the id_token is given, the granted authorization for every EVSE where this id_token is placed will be withdrawn If both parameters are given, the granted authorization for the given EVSE will be withdrawn, if the placed id_token matches the given id_token. If no parameter is given, all granted authorizations for all EVSEs will be removed

  • WithdrawAuthorizationResult
    string

    The result of a WithdrawAuthorizationRequest: Accepted in case requested authorization was removed AuthorizationNotFound in case no match for request was found EvseNotFound in case no match for evse_id was found Rejected in case module could not process the request for other reasons

      Allowed values:
    • "Accepted"
    • "AuthorizationNotFound"
    • "EvseNotFound"
    • "Rejected"
  • 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