mutation execute {
startJob(
#fileId or fileVersionId are required. If both are passed, the fileVersionId is used.
fileId: "881189d3-59b8-48d7-84fe-3199bdfbc40a",
#fileVersionId: "3f5f04d4-23f4-4cd8-a9ba-70814952dff7",
#Device IDs OR Tags are used to identify the devices for the job. If both device IDs and tags are passed, device Ids will be used.
deviceIds: ["80:00:00:00:01:22:37:AE"],
#optional device tags (can be used to run a group of scripts against a set of devices with these tags at time of execution)
#ANY/ALL (i.e. or/and), when tags are used, operator should accompany
tagFilter: {operator: ANY, values:["reboot"]},
arguments: [
{
name: "url"
value: "https://remote.it"
},
{
name: "imageFile"
value: "3f5f04d4-23f4-4cd8-a9ba-70814952dff7"
},
{
name: "bookmarkName"
value: "RemoteIt"
},
{
name: "action"
value: "Add"
}
]
)
}
query GetJobs {
login {
# Add the following line if you need to do this in Org context.
# The ID is the Org ID
#account(id:"XXXXXX-XXXX-XXXXXX-XXXXX") {
#see documentation on paginated responses for iteration
#examples of filtering below
jobs(ids: ["41fc0cec-4efd-40ef-8e48-1aa109019f1c","41fc0cec-4efd-40ef-8e48-xxxxx"], statuses:[FAILED,WAITING,RUNNING,SUCCESS,CANCELLED],size: 1000)
{
hasMore
total
last
items {
id
owner {
email
}
user {
email
}
created
updated
# One of the following FAILED,WAITING,RUNNING,SUCCESS,CANCELLED
status
#tags associated with job
tags {
name
}
#ANY/ALL (i.e. or/and)
tagOperator,
fileVersion {
id
file {
name
}
}
jobDevices {
id
device {
id
}
#attributes associated with the job.
attributes {
created
id
key
value
}
#one of the following: FAILED,WAITING,RUNNING,SUCCESS,CANCELLED
status
}
arguments {
id
fileArgument {
id
name
desc
order
options
argumentType
created
}
name
desc
order
argumentType
value
}
}
}
}
}
The FileArgument this J
obArgument is based on
| **Device Attributes** | Attribute | Data Type | Description | | --------- | --------- | ------------------------------------------------------------------ | | created | Date | DateTime of the Attributes creation in ISO 8601 format Date String | | id | String | The primary key of the Job Device. | | name | String | Name of the attribute | | value | String | Value of the attribute | ## Pagination The list responses from the versions and jobs queries return paginated results. We implement a pagination model with `from`/`after` and `size` pagination arguments. Responses can return `hasMore`, `last` and `total` . If the `hasMore` response returns true, this indicates do another fetch. For example if your size is 100 and hasMore returns true, the `from` will increment to 101 to fetch the next set. You could also determine this by iteration until you get to the `total`. Size is limited to 1000 max in each return. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.remote.it/developer-tools/api/usage/scripting.md?ask=