Skip to main content
POST
Bulk Command
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.
string
required
The OCPP 1.6 command name (e.g. Reset, ChangeAvailability, UnlockConnector, TriggerMessage, ChangeConfiguration).
object
Command-specific payload forwarded to each charger. Optional. Shape depends on the command.
array
required
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.
string
Unique identifier of the bulk run. Use this with GET /v3/chargers/commands/bulk/{run} to poll progress.
string
The OCPP command that was queued.
object
The command payload forwarded to each charger.
string
running while jobs are in flight, completed once every charger has a terminal result.
integer
Number of chargers submitted.
integer
Chargers that acknowledged the command.
integer
Chargers that were offline when the command was dispatched.
integer
Chargers whose command failed for any other reason (message in the per-result payload).
integer
Chargers the authenticated user does not have access to, or that could not be resolved.
string
When the run was created (ISO 8601 date-time).
string
When every charger reached a terminal result (ISO 8601 date-time). null while the run is still in progress.
array
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.