Queues the same OCPP 1.6 command against multiple chargers at once. Each charger is processed by a background job; the response returns a run resource you can poll to track progress.
Chargers the authenticated user cannot access are silently reported as skipped_forbidden in the run results. Chargers that are offline at dispatch time are reported as offline. Other failures are reported as error with a message.
The OCPP 1.6 command name (e.g. Reset, ChangeAvailability, UnlockConnector, TriggerMessage, ChangeConfiguration).
Command-specific payload forwarded to each charger. Optional. Shape depends on the command.
UUIDs of the target chargers. Minimum 1, no hard upper bound — result rows are inserted in batches and one queue job is dispatched per accessible charger.
Response
Returns 202 Accepted with the created run wrapped in data.
Unique identifier of the bulk run. Use this with GET /v3/chargers/commands/bulk/{run} to poll progress.
The OCPP command that was queued.
The command payload forwarded to each charger.
running while jobs are in flight, completed once every charger has a terminal result.
Number of chargers submitted.
Chargers that acknowledged the command.
Chargers that were offline when the command was dispatched.
Chargers whose command failed for any other reason (message in the per-result payload).
Chargers the authenticated user does not have access to, or that could not be resolved.
Per-charger status. Each entry contains charger_uuid, status (pending, sent, offline, error, skipped_forbidden), message, executed_at, and — when the user has access — an embedded charger object with uuid, identity, and reference.