- Reference
- OCPI 2.2.1 (eMSP)
- Sender async ChargingProfile result
OpenAPI reference
Sender async ChargingProfile result
/chargingprofiles/result/{request_id}Receive the asynchronous response from the Charge Point for a previously issued ChargingProfile request (GET ActiveChargingProfile / PUT SetChargingProfile / DELETE). The ``request_id`` path segment m
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
POST /chargingprofiles/result/{request_id}Absolute URL: https://ocpi-api.gridos.co/ocpi/emsp/2.2.1/chargingprofiles/result/{request_id}
Receive the asynchronous response from the Charge Point for a previously issued ChargingProfile request (GET ActiveChargingProfile / PUT SetChargingProfile / DELETE). The request_id path segment matches the suffix the eMSP embedded in the response_url it supplied to the CPO.
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 POST 'https://ocpi-api.gridos.co/ocpi/emsp/2.2.1/chargingprofiles/result/example' \
-H "Authorization: Token $OCPI_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"result":"ACCEPTED","profile":{"start_date_time":"2026-03-28T10:00:00Z","charging_profile":{"charging_rate_unit":"W","charging_profile_period":[{"start_period":0,"limit":11000}]}}}'Request
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
request_id | string | Yes | Identifier of the ChargingProfile request. |
Request body
application/json · Required
Schema: ActiveChargingProfileResult
| Field | Type | Required | Description |
|---|---|---|---|
result | `"ACCEPTED" | "REJECTED" | "UNKNOWN"` |
profile | ActiveChargingProfile | No | ActiveChargingProfile |
Request examples
Example 1
{
"result": "ACCEPTED",
"profile": {
"start_date_time": "2026-03-28T10:00:00Z",
"charging_profile": {
"charging_rate_unit": "W",
"charging_profile_period": [
{
"start_period": 0,
"limit": 11000
}
]
}
}
}Example 2
{
"result": "REJECTED"
}Responses
| Status | Description | Schema |
|---|---|---|
200 | Successful Response | BaseResponse |
400 | Invalid or missing parameters (HTTP 200, OCPI envelope) | — |
401 | Unauthorized | — |
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"
}400 — invalid or missing parameters (HTTP 200, OCPI envelope)
application/json
Response example
{
"status_code": 2001,
"status_message": "Invalid or missing parameters",
"timestamp": "2025-01-01T00:00:00Z",
"doc_url": "https://github.com/ocpplab/ocpi-gateway/blob/main/docs/errors.md#2001-invalid-parameters",
"errors": [
{
"field": "country_code",
"message": "expected 'NL' to match Token A identity",
"type": "value_error.identity_mismatch"
}
]
}401 — unauthorized
application/json
Response example
{
"status_code": 2001,
"status_message": "Unauthorized",
"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 POST 'https://ocpi-api.gridos.co/ocpi/emsp/2.2.1/chargingprofiles/result/example' \
-H "Authorization: Token $OCPI_TOKEN" \
-H 'Content-Type: application/json' \
-d '{"result":"ACCEPTED","profile":{"start_date_time":"2026-03-28T10:00:00Z","charging_profile":{"charging_rate_unit":"W","charging_profile_period":[{"start_period":0,"limit":11000}]}}}'