Get Device Daemon Permissions

> Tool Name: airdroid_business_device_daemon_permissions_get

> Risk Level: Read

> Execution Mode: Synchronous

> Category: Device Management

Quick Start

Summary: Read the AirDroid Biz Daemon permission items reported for one device. This is not a device operating-system permission list.

You need: DeviceId from List Devices or Get a Device by Name.

Success criteria: StatusCode == 200 and ErrorMessage is empty. The result can contain an empty Permissions array; do not require a non-empty array to determine whether the request succeeded.

Next step: Use each Permissions[].Name and Permissions[].Status item to diagnose the relevant daemon capability.

Minimal request example:

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Minimal response example:

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d",
  "Permissions": [
    {
      "Name": "Remote Control",
      "Status": "Enabled"
    }
  ],
  "Hint": "",
  "Retryable": false,
  "OriginalStatusCode": 200,
  "StatusCode": 200,
  "ErrorMessage": ""
}

Recipes

Recipe 1: Inspect one device

When to use: A daemon-backed device capability needs investigation.

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Recipe 2: Resolve a device ID before inspecting it

When to use: You have a device name rather than its ID.

{
  "DeviceName": "Store-Kiosk-01"
}

This request is for Get a Device by Name. Pass its returned device ID to this action.

Recipe 3: Review unsupported or disabled daemon items

When to use: A returned permission item has Status Disable or Not Supported.

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

Read the returned Permissions array and handle each reported item by its exact Name and Status.

1. Overview

1.1 Description

Returns Biz Daemon permission-detail items for one device. Each item contains only the Admin Console permission label and its reported grant state.

1.2 When to Use

• Diagnose a daemon-backed feature on one device.
• Inspect whether a returned permission item is Enabled, Disable, or Not Supported.
• Obtain detail after using Search Devices for a daemon-status summary.

1.3 Execution Mode and Response

This is a synchronous read. It immediately returns the echoed or upstream DeviceId, a Permissions array, and standard status fields.

1.4 Prerequisites

1.5 Prerequisite Tools

1.6 Similar Tools

Use Search Devices with daemon_status when you only need the aggregate All Granted or Some not granted summary. Use this action when you need reported item-level details.

2. Inputs

2.1 Parameter List

2.2 Parameter Details

`DeviceId`

• Must be a non-empty string.
• Obtain it from List Devices or Get a Device by Name.
• Use an Android device ID; Windows devices are unsupported for this permission-detail request.

2.3 Parameter Combination Logic

This action accepts one DeviceId only. To inspect several devices, make one call per device after selecting the targets.

3. Outputs

3.1 Response Examples

Success:

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d",
  "Permissions": [
    {
      "Name": "Policy & Kiosk",
      "Status": "Not Supported"
    }
  ],
  "Hint": "",
  "Retryable": false,
  "OriginalStatusCode": 200,
  "StatusCode": 200,
  "ErrorMessage": ""
}

Validation failure:

{
  "DeviceId": "",
  "Permissions": [],
  "Hint": "Obtain device_id via 'List Devices' or 'Get a Device by Name', then retry.",
  "Retryable": false,
  "OriginalStatusCode": 0,
  "StatusCode": -1,
  "ErrorMessage": "DeviceId is required."
}

3.2 Field Descriptions

3.3 Permission Status Values

4. Examples

4.1 Check one Android device

{
  "DeviceId": "fa6edcff65ab444e8b5e0eb08df4175d"
}

4.2 Empty device ID

{
  "DeviceId": ""
}

This returns StatusCode -1 and ErrorMessage DeviceId is required.

4.3 Unsupported Windows device

Use an Android device ID instead. The runtime returns the upstream failure in ErrorMessage and a hint stating that Biz Daemon permission details are unsupported on Windows devices.

5. Error Handling

5.1 StatusCode Semantics

5.2 Common Errors

5.3 Retry Decision

Follow the Retryable field. The runtime marks rate-limit, timeout, and network-request failures as retryable, but validation and unsupported-target failures require correction first.

6. Best Practices

6.1 Start with the narrowest lookup

Use this action for one device after a targeted diagnostic. Use Search Devices with daemon_status to narrow a larger population first.

6.2 Preserve the reported values

Treat Permissions[].Name and Permissions[].Status as the response contract. Do not infer unreturned permission items or OS-level states.

7. Related Tools

8. Tool Chains

8.1 Diagnose a daemon feature

Search Devices -> Get Device Daemon Permissions

1. Use Search Devices to identify a device that needs detail.
2. Pass its DeviceId to this action.
3. Use the returned Permissions items to identify the reported daemon permission state.