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
GET /api/v2/devices?teamId=1 HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Successful response
{
"devices": [
{
"id": 2,
"name": "Phone",
"teamId": 2,
"udid": "XboVPMTfgtwBNjRr7AGPe9X4AdRZhkaF",
"scope": [
"call",
"scaner"
],
"info": null,
"queueCount": 0,
"queueLimit": 10000,
"scenarioId": null
}
]
}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
GET /api/v2/devices/{deviceId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Successful response
{
"device": {
"id": 2,
"name": "Phone",
"teamId": 2,
"udid": "XboVPMTfgtwBNjRr7AGPe9X4AdRZhkaF",
"scope": [
"call",
"scaner"
],
"info": null,
"queueCount": 0,
"queueLimit": 10000,
"scenarioId": null
}
}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
DELETE /api/v2/devices/{deviceId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Accept: */*
Successful response
{
"device": 2
}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
PATCH /api/v2/devices/{deviceId} HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 24
{
"name": "Android phone"
}Successful response
{
"device": {
"id": 2,
"name": "Android phone",
"teamId": 2,
"udid": "XboVPMTfgtwBNjRr7AGPe9X4AdRZhkaF",
"scope": [
"call",
"scaner"
],
"info": null,
"queueCount": 0,
"queueLimit": 10000,
"scenarioId": null
}
}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
POST /api/v2/devices/request HTTP/1.1
Host: eu1.make.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 27
{
"name": "Phone",
"teamId": 1
}Successful response
{
"createDeviceRequest": {
"udid": "k1KqeAVIYA5Rq5vduiU3mUfbGD4vhTfH",
"inspector": true
}
}Last updated

