Skip to main content
POST
Create or replace a charger-level limit lock

Authorizations

Authorization
string
header
required

OAuth 2.0 access token obtained via POST /oauth/token with client_credentials grant. Tenant and scopes are embedded in the JWT. No additional headers needed.

Path Parameters

controllerUuid
string
required

The charger's unique controller identifier.

connectorId
string
required

The connector number on the charger, e.g. "1" for a single-connector charger.

Body

application/json
startTime
string<date-time>
required

ISO-8601 UTC timestamp. Required.

Example:

"2026-06-12T08:00:00Z"

endTime
string<date-time>
required

ISO-8601 UTC timestamp. Must be after startTime and in the future. Required.

Example:

"2026-06-12T18:00:00Z"

limitKw
number<float>
required

Power limit in kW. Must be greater than 0. Required.

Example:

50

priority
integer
default:0

OCPP-stack-style priority level, 0 (lowest) to 10 (highest). Submitting a profile at a priority that already exists for this target replaces it.

Required range: 0 <= x <= 10
Example:

5

Response

Charger schedule created/replaced

controllerUuid
string
Example:

"a1b2c3d4-e5f6-7890-abcd-ef1234567890"

connectorId
string
Example:

"1"

limitKw
number
Example:

11

startTime
string<date-time>
endTime
string<date-time>
status
enum<string>
Available options:
SCHEDULED,
ACTIVE,
EXPIRED