GET
/
examples
/
ocpp-charging-profile
Get Example Ocpp Charging Profile
curl --request GET \
  --url https://api-sandbox.axle.energy/examples/ocpp-charging-profile \
  --header 'Authorization: Bearer <token>'
{
  "connectorId": 123,
  "csChargingProfiles": {
    "chargingProfileId": 123,
    "transactionId": 123,
    "stackLevel": 123,
    "chargingProfilePurpose": "ChargePointMaxProfile",
    "chargingProfileKind": "Absolute",
    "recurrencyKind": "Daily",
    "validFrom": "2023-11-07T05:31:56Z",
    "validTo": "2023-11-07T05:31:56Z",
    "chargingSchedule": {
      "duration": 123,
      "startSchedule": "2023-11-07T05:31:56Z",
      "chargingRateUnit": "W",
      "chargingSchedulePeriod": [
        {
          "startPeriod": 123,
          "limit": 123,
          "numberPhases": 123
        }
      ],
      "minChargingRate": 123
    }
  }
}

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Response

Example OCPP charging profile

A SetChargingProfileRequest object, as defined in section 6.43 of the OCPP 1.6 documentation at https://openchargealliance.org/protocols/open-charge-point-protocol/#OCPP1.6

This is used by the central system to send charging profiles to an EV charger.

​
connectorId
integer
required

The connector to which the charging profile applies. If connectorId = 0, the message contains an overall limit for the Charge Point.

​
csChargingProfiles
object
required

The charging profile to be set at the Charge Point. A ChargingProfile consists of a ChargingSchedule, describing the amount of power or current that can be delivered per time interval.