Set a charging profile on a partner session (2.2.1 / 2.3.0)
Asks the CPO to apply a charging profile to a session it runs. The CPO answers asynchronously. OCPI 2.2.1 and 2.3.0 only.
Authentication
AuthorizationBearer
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
version
OCPI version: 221 (2.2.1) or 230 (2.3.0). OCPI 2.1.1 has no charging profiles or charging preferences.
Allowed values:
session_id
Query parameters
partner_id
Roaming partner to talk to: the roaming_partner_id from GET /ocpi/partners, not its id.
to_country_code
Partner is a Hub: country code of the CPO behind it (OCPI-to-country-code). Set together with to_party_id; through a Hub the request is refused (400) when neither is set and the target is not cached.
to_party_id
Partner is a Hub: party id of the CPO behind it (OCPI-to-party-id). Set together with to_country_code.
Request
This endpoint expects an object.
charging_profile
OCPI ChargingProfile (same shape in 2.2.1 and 2.3.0).
Response
Successful Response
partner_id
operation
session_id
result
response_result
timeout
http_status
ocpi_status_code
duration_ms
error
Errors
400
Bad Request Error
401
Unauthorized Error
404
Not Found Error
422
Unprocessable Entity Error
429
Too Many Requests Error
502
Bad Gateway Error
504
Gateway Timeout Error