Charging Profiles
Overview
Smart charging lets a party shape how fast a car charges over time, sending a limit on power or current to a running session instead of a fixed target. Charge points sit on slow links, so the module works asynchronously like Commands: the sender requests a profile, the receiver acknowledges it can forward the request, and the real result arrives later as a POST to a response URL.
EMSP or Smart Charging Provider (Sender)
CPO (Receiver)
Key Fields
| Field | Type | Description |
|---|---|---|
start_date_time | DateTime | Start of an absolute profile; if absent it is relative to charging start |
duration | int | Length of the profile in seconds |
charging_rate_unit | ChargingRateUnit | W (power) or A (current per phase) |
charging_profile_period | ChargingProfilePeriod[] | Maximum power or current usage over time |
response_url | URL | Where the asynchronous result is POSTed back |
Endpoints
/ocpi/2.2.1/chargingprofiles/{session_id}
/ocpi/2.2.1/chargingprofiles/{session_id}
/ocpi/2.2.1/chargingprofiles/{session_id}
Live Endpoint Tester
Send requests directly to the local backend and see the response.