Skip to main content
API

Send a charging profile to the charger​

x-ms-visibility: "important"

Send the charging profile request to the charger. The charging profile can be either TxDefaultProfile or TxProfile. If profile is related to a transaction, transactionId or evseTransactionId has to be set

Path Parameters
    chargerId string required

    This is globally an unique ID for the charger

Request Body required

ChargingProfile body follows the OCPP standards profile structure.

    socketId int32
    transactionId int32

    Is used to identify a transaction when the charger supports OCPP 1.6

    evseTransactionId string

    Is used to identify a transaction when the charger supports OCPP 2.0.1

    chargingProfileId int32 nullable
    stackLevel int32
    chargingProfilePurpose string
    chargingProfileKind string
    recurrencyKind string
    validFrom date-time nullable
    validTo date-time nullable
    duration int32 nullable
    startSchedule date-time nullable
    chargingRateUnit string
    minChargingRate float nullable
    schedule object[]
  • Array [
    • startPeriod int32
    limit float
    numberPhases int32 nullable
  • ]
    • sessionId string

    Can be used to identify a transaction when it has been started through OCPI

Responses

Charging profile created and sent successfully

Schema

    string

Loading...