Execute Fleet Action

Execute a bulk action on all devices in the fleet. The action is processed asynchronously and a bulk_response_id is returned to track progress. For 'issue_command' and 'send_configuration' actions, only eligible devices will receive the command/setting.

Path Params
string
required

The ID that specifies a Fleet

Body Params
string
enum
required

The type of action to execute on fleet devices.

Allowed:
string

The ID of a user-defined command to execute. Required for 'issue_command' action when using a user-defined command. Mutually exclusive with 'gateway_command'.

string

The name of a gateway command to execute (e.g., 'reboot', 'update'). Required for 'issue_command' action when using a gateway command. Mutually exclusive with 'command_id'.

tags
array of strings

An array of tags to add to all devices in the fleet. Required for 'add_tags' action.

tags
metadata
object

Key/value pairs to add to all devices in the fleet. Required for 'add_metadata' action.

integer
≥ 1

The heartbeat period in seconds to set on devices. Used for 'update_heartbeat' action.

heartbeat_values
array of strings

An array of heartbeat values to set on devices. Used for 'update_heartbeat' action.

heartbeat_values
string

The configuration ID for validation. Required for 'send_configuration' action.

string

The setting ID to send to devices. Required for 'send_configuration' action.

integer
Defaults to 0

The setting version to send. Use 0 for the latest version. Used for 'send_configuration' action.

string

The command ID used to send the setting to devices. Required for 'send_configuration' action.

Responses

400

The request was malformed or contained invalid parameters.

401

You are not authorized

403

You are forbidden from accessing this resource

404

The item you were looking for does not exist

500

An unexpected error was encountered.

Language
Credentials
Header
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json