- Reference
- OCPI 2.2.1 (eMSP)
- Sender ActiveChargingProfile update
OpenAPI reference
Sender ActiveChargingProfile update
/chargingprofiles/{session_id}The Receiver (typically CPO) informs the Sender (typically eMSP/SCSP) that the ActiveChargingProfile changed for an ongoing session that the Sender previously set a profile on. The eMSP forwards the s
API: OCPI 2.2.1 (eMSP) · Module: Charging Profiles (eMSP Sender)
Base path:/chargingprofiles· Base URL:https://ocpi-api.gridos.co/ocpi/emsp/2.2.1
Overview
PUT /chargingprofiles/{session_id}Absolute URL: https://ocpi-api.gridos.co/ocpi/emsp/2.2.1/chargingprofiles/{session_id}
The Receiver (typically CPO) informs the Sender (typically eMSP/SCSP) that the ActiveChargingProfile changed for an ongoing session that the Sender previously set a profile on. The eMSP forwards the snapshot to the SCSP downstream of this gateway.
Requires authentication. Use Authorization: Token <token>. See OCPI credentials.
How to call
Quick Shell sample (set OCPI_TOKEN when auth is required). Full Python and TypeScript under Examples.
curl -sS -X PUT 'https://ocpi-api.gridos.co/ocpi/emsp/2.2.1/chargingprofiles/SESSION1' \
-H "Authorization: Token $OCPI_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"start_date_time":"2026-03-28T10:00:00Z","charging_profile":{"charging_rate_unit":"W","charging_profile_period":[{"start_period":0,"limit":11000},{"start_period":3600,"limit":7000}]}}'Request
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Session.id of the Session object. |
Request body
application/json · Required
Schema: ActiveChargingProfile
| Field | Type | Required | Description |
|---|---|---|---|
start_date_time | string (date-time) | Yes | — |
charging_profile | ChargingProfile | Yes | ChargingProfile |
Request example
{
"start_date_time": "2026-03-28T10:00:00Z",
"charging_profile": {
"charging_rate_unit": "W",
"charging_profile_period": [
{
"start_period": 0,
"limit": 11000
},
{
"start_period": 3600,
"limit": 7000
}
]
}
}Responses
| Status | Description | Schema |
|---|---|---|
200 | Successful Response | BaseResponse |
401 | Unauthorized | — |
404 | Not Found | — |
422 | Validation Error | HTTPValidationError |
200 — successful response
application/json
Schema: BaseResponse
| Field | Type | Required | Description |
|---|---|---|---|
status_code | integer | No | Default: 1000 |
status_message | string | No | — |
timestamp | string (date-time) | No | — |
Response example
{
"status_code": 1000,
"status_message": "Success",
"timestamp": "2024-01-15T10:00:00Z"
}401 — unauthorized
application/json
Response example
{
"status_code": 2001,
"status_message": "Unauthorized",
"timestamp": "2025-01-01T00:00:00Z"
}404 — not found
application/json
Response example
{
"status_code": 2001,
"status_message": "Session not found",
"timestamp": "2025-01-01T00:00:00Z"
}422 — validation error
application/json
Schema: HTTPValidationError
| Field | Type | Required | Description |
|---|---|---|---|
detail | ValidationError[] | No | Detail |
Response example
{
"detail": [
{
"loc": [],
"msg": "string",
"type": "string",
"input": {
"_type": "Input"
},
"ctx": {
"_type": "Context"
}
}
]
}Examples
Shell, Python, and TypeScript (set OCPI_TOKEN when auth is required).
curl -sS -X PUT 'https://ocpi-api.gridos.co/ocpi/emsp/2.2.1/chargingprofiles/SESSION1' \
-H "Authorization: Token $OCPI_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"start_date_time":"2026-03-28T10:00:00Z","charging_profile":{"charging_rate_unit":"W","charging_profile_period":[{"start_period":0,"limit":11000},{"start_period":3600,"limit":7000}]}}'