Skip to main content
POST
Create or replace a location priority limit profile

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

locationId
string
required

The location's unique identifier.

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

Profile created/replaced

locationId
string
Example:

"3632155"

priority
integer
Example:

5

limitKw
number
Example:

50

startTime
string<date-time>
endTime
string<date-time>
status
enum<string>
Available options:
SCHEDULED,
ACTIVE,
EXPIRED
permanentLimitKw
number | null
Example:

100

effectiveLimitKw
number | null
Example:

50