Stop, restart, or delete deployed charger runtimes
A single deployment_id runs synchronously and returns per-charger results. A location_id covers every charger in the location: it returns 202 at once and runs in the background, so follow it with GET /evcharger/deployment-runtime-ops/status (client.evcharger.deployment_runtime_ops.status()) until each charger reaches its target state. Background work is not durable across restarts.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Runtime operation to apply: stop, restart, or delete.
One deployment id to operate on. Mutually exclusive with location_id.
Operate on every deployment in this location. Mutually exclusive with deployment_id.
Response
202 acknowledgment for work handed off to a background task.
Long-running fan-outs (location create, location runtime ops) return this immediately; the actual work runs in the background and is not awaited.