Devices
Get a list of devices of a given team.
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
1true = devices with scenarioId; false = devices without scenarioId - this filter only affects the trigger scope
trueDevices assigned to the scenario and not assigned devices. If this parameter is set assigned parameter is ignored.
4Successful response
Successful response
The ID can be id or udid.
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
1Successful response
Successful response
Errors: IM004 - Confirmation required (error with metadata) - needs confirmation IM405 - Device can't be deleted because it contains messages in queue (error with metadata) - needs confirmation IM005 - Device is locked by a running scenario and thus can't be deleted
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
2trueSuccessful response
Successful response
Update a device
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
Successful response
Successful response
Required scope: devices:write
Authorize the API call with your API token in the Authorization header with the value: Token your-api-token.
If you don't have an API token yet, please refer to the "Authentication" section to learn how to create one.
1Successful response
Successful response
Last updated

