# Get all Operations in the Tenant Endpoint: GET /v0/operations/ Version: 1.0.0 Security: apiKey ## Query parameters: - `limit` (integer) - `offset` (integer) - `state` (integer) Following are the Operation States and their corresponding integer values OPERATION_CREATED = 10 OPERATION_RESOLVING = 20 OPERATION_RESOLVED = 30 OPERATION_DISPATCHING = 40 OPERATION_DISPATCHED = 50 OPERATION_PROCESSING = 60 OPERATION_COMPLETED = 70 OPERATION_SUCCESS = 80 OPERATION_FAILURE = 90 OPERATION_SCHEDULED = 100 OPERATION_CANCELLED = 110 OPERATION_TIMEOUT = 120 - `ordering` (string) Field to order the results by. Prefix with '-' to reverse the order. Enum: "created_at", "state", "updated_at" - `operation_type` (string) Filter operations by type (e.g., INSTALL, UNINSTALL, CONVERGE, APP_INSTALL, APP_UNINSTALL, REBOOT) - `group_multi` (string) Filter by multiple group ID. Fetch the devices from groups matching with the IDs and it's subgroup. ## Response 200 fields (application/json): - `content` (object) - `content.count` (integer) - `content.previous` (string) - `content.next` (string) - `content.results` (array) - `content.results.id` (string) - `content.results.operation` (string) Enum: "CONVERGE" - `content.results.state` (string) Enum: "CREATED", "RESOLVING", "RESOLVED", "DISPATCHING", "COMPLETED", "FAILED" - `content.results.schedule_type` (string) Following Schedule types are supported ``` * IMMEDIATE: Schedule the command to execcute Immediately * WINDOW: Schedule the command to execute within the given window Enum: "IMMEDIATE", "WINDOW" - `content.results.schedule_args` (object) - `content.results.schedule_args.start_datetime` (string) Start date and time in ISO 8601 format, including timezone (e.g., 2024-08-08T14:30:00Z or 2024-08-08T14:30:00+05:30). - `content.results.schedule_args.end_datetime` (string) End date and time in ISO 8601 format, including timezone (e.g., 2024-08-08T15:30:00Z or 2024-08-08T15:30:00+05:30). - `content.results.schedule_args.time_type` (string) The Time-Type argument, in Schedule args, is to indicate which timezone the Command Framework should utilize when scheduling the command. Following Schedule Args for Time-Type are supported: * CONSOLE: Use the local timezone of the user creating the schedule. * DEVICE: Use the local timezone of the device, to which the command is issued, wherever it may be. Enum: "console", "device" - `content.results.schedule_args.window_start_time` (string) It is automatically populated by the time field from the request's start_datetime and cannot be injected via the API request body. - `content.results.schedule_args.window_end_time` (string) It is automatically populated by the time field from the request's end_datetime and cannot be injected via the API request body. - `content.results.schedule_args.days` (array) - `content.results.operation_device_query` (object) - `content.results.arguments` (object) - `content.results.arguments.converge_with_provision` (boolean) - `content.results.arguments.sample_key` (string) - `content.results.reason` (string) - `content.results.created_at` (string) - `content.results.created_by` (string) - `content.results.updated_at` (string) - `content.results.updated_by` (string) - `content.results.operation_activity` (array) - `content.results.operation_activity.operation_state` (string) Enum: "CREATED", "QUERY INITIATED", "QUERY RESOLVED", "DISPATCHING", "DISPATCHED", "PROCESSING", "SUCCESS", "FAILURE" - `content.results.operation_stats` (object) - `content.results.operation_stats.device_operation_statuses_count` (object) - `content.results.operation_stats.device_operation_statuses_count.resolved_device_count` (integer) - `content.results.operation_stats.device_operation_statuses_count.dispatched_device_count` (integer) - `content.results.operation_stats.device_operation_statuses_count.dispatch_failed_count` (integer) - `content.results.operation_stats.device_operation_statuses_count.failed_device_count` (integer) - `content.results.operation_stats.device_operation_statuses_count.success_device_count` (integer)