Update charger configuration​

POST
/chargers/{chargerId}/configuration/set

Sends a value for one charger configuration key. The response reports whether the charger must reboot for the change to take effect.

Use cases

  • Apply an OCPP configuration change to a charger.
  • Check rebootRequired before scheduling a restart.

Related endpoints

  • GET /chargers/{chargerId} — inspect the charger and its current configuration.
  • POST /chargers/{chargerId}/restart — restart the charger when required.

Authorizations​

bearerAuth

Generate an API token here

Type
HTTP (bearer)

Parameters​

Header Parameters

compatibility-date*

API compatibility date in YYYY-MM-DD format. Must be a date after 2025-11-01.

Type
string
Required
Example"2025-11-02"
Pattern
^\d{4}-\d{2}-\d{2}$
organization-id*

Routes the request to the organization named by this ID. The bearer token must be authorized for that organization.

Type
string
Required
Example"3b241101-e2bb-4255-8caf-4136c566a962"
Min Length
1
Max Length
40

Path Parameters

chargerId*

UUID returned by POST /chargers or GET /chargers. Use it to target that charger for configuration, connector, or status operations.

Type
string
Required
Example"550e8400-e29b-41d4-a716-446655440000"
Min Length
1
Max Length
40

Request Body​

application/json

OCPP configuration key; the charger response lists the keys it supports.

Max Length40

Value to send for the key. Match the type and allowed values reported in the charger configuration.

Responses​

success.charger.configuration.update

application/json

Playground​

Authorization
Headers
Variables
Key
Value
Body

Samples​