Create or replace a charger-level limit lock

curl --request POST \ --url https://api.ridergy.com/v1/chargers/{controllerUuid}/connectors/{connectorId}/schedules \ --header 'Content-Type: application/json' \ --header 'x-api-key: <api-key>' \ --data ' { "startTime": "2026-06-12T08:00:00Z", "endTime": "2026-06-12T18:00:00Z", "limitKw": 11, "priority": 5 } '

Authorizations

x-api-key

string

header

required

Per-tenant API key. Tenant is derived from the key — never from the request.

Path Parameters

controllerUuid

string

required

connectorId

string

required

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