Charging Profiles
Charging Profiles in OCPI 2.2.1
A Charging Profile requests a maximum limit over time for an ongoing Session. It does not promise that the EV will charge at that limit. This relative profile limits current to 16 A per phase; local limits and the EV can reduce the actual rate.
Sources (5)
Example payload · set-relative-current-profile
{
"charging_profile": {
"charging_rate_unit": "A",
"charging_profile_period": [
{
"start_period": 0,
"limit": 16
}
]
},
"response_url": "https://sender.example.invalid/results/example-profile"
}Which endpoints does this module define?
These paths illustrate the requests. Use the URLs advertised by your partner, replace the placeholders and choose the matching interface. A listed method does not establish that this site's simulator implements it.
CPO · receiver interface
Gets the ActiveChargingProfile for a specific charging session.
GET/ocpi/ 2.2.1/ chargingprofiles/ {session_id}?duration={duration}&response_url={response_url} Creates/updates a ChargingProfile for a specific charging session.
PUT/ocpi/ 2.2.1/ chargingprofiles/ {session_id} Cancels an existing ChargingProfile for a specific charging session.
DELETE/ocpi/ 2.2.1/ chargingprofiles/ {session_id}?response_url={response_url}
Source
eMSP / SCSP · sender interface
Receive the asynchronous response from the Charge Point.
POST{response_url}Receiver (typically CPO) can send an updated ActiveChargingProfile when other inputs have made changes to existing profile.
PUT/ocpi/ 2.2.1/ chargingprofiles/ {session_id}
Source
Try an endpoint
Send a request to this site's OCPI endpoints and read the answer. It never reaches your own system.