Datto RMM Device Management

Overview

Devices are the core managed entities in Datto RMM. Each device represents an endpoint with the Datto agent installed - workstations, servers, ESXi hosts, or network devices. This skill covers device identification, status monitoring, user-defined fields, and common device operations.

Anti-triggers

• The billable or contracted record for the same machine — use

autotask-configuration-items.

• The documentation record for the same machine — use

itglue-configurations.

• Hardware specs or installed software — those come from the

periodic audit, not the device record; use datto-rmm-audit.

• A security sensor rather than the RMM agent — an endpoint

commonly runs both; use rocketcyber-agents.

• The same endpoint under a different RMM — "device" means the

managed endpoint in most of them, so the wording never disambiguates; confirm which agent is enrolled, then use ncentral-devices, ninjaone-devices, or atera-agents (Atera reserves "device" for agentless monitors).

Key Concepts

Device Identifiers

Every device has multiple identifiers:

Device Types

Device Status

Field Reference

Devices carry identifier, site, type/status, network, OS, hardware, agent, and timestamp fields, plus 30 user-defined fields (udf1-udf30, 255 char max, commonly used for asset tag, department, primary user, location, purchase date, lease expiration). See references/fields.md for the complete Device interface and UDF table.

Common Workflows

Device Lookup by Hostname

async function findDeviceByHostname(client, hostname) {
  // Fetch all devices (with pagination)
  const allDevices = [];
  let url = '/api/v2/devices?max=250';

  while (url) {
    const response = await client.request(url);
    allDevices.push(...response.devices);
    url = response.pageDetails?.nextPageUrl;
  }

  // Search case-insensitive
  const matches = allDevices.filter(d =>
    d.hostname.toLowerCase().includes(hostname.toLowerCase())
  );

  if (matches.length === 0) {
    return { found: false, suggestions: [] };
  }

  if (matches.length === 1) {
    return { found: true, device: matches[0] };
  }

  return {
    found: false,
    ambiguous: true,
    suggestions: matches.map(d => ({
      hostname: d.hostname,
      uid: d.uid,
      site: d.siteName
    }))
  };
}

Equivalent lookups by IP and MAC address, an offline-device report, and a bulk UDF update helper follow the same pagination pattern - see references/examples.md for the full implementations, including UDF/description length validation.

API Patterns

• GET /api/v2/devices?max=250 - list all devices (paginated via pageDetails.nextPageUrl)
• GET /api/v2/device/{deviceUid} - get a single device
• GET /api/v2/site/{siteUid}/devices?max=250 - devices scoped to a site
• POST /api/v2/device/{deviceUid} - update device fields (description, UDFs)
• DELETE /api/v2/device/{deviceUid} - remove device from Datto RMM (does not uninstall the agent)

See references/api.md for full request/response examples.

Gotchas

• Deleting a device does not uninstall the agent - it only removes the device record from Datto RMM.
• UDF values are capped at 255 characters; description is capped at 1000. Both fail with 400 Invalid field value when exceeded.
• `status` can lag behind real connectivity. Combine it with lastSeen to determine effective status - see getDeviceEffectiveStatus in references/examples.md.
• MAC addresses arrive in inconsistent formats (colons, dashes, none) - normalize before comparing.
• Use `deviceUid`, not hostname, for lookups and updates - hostnames are not guaranteed unique across sites.
• Respect rate limits on bulk operations (e.g., a short sleep between sequential per-device requests).

See references/errors.md for the full device API error table.

Related Skills

• Datto RMM Alerts - Device alert management
• Datto RMM Audit - Device hardware/software inventory
• Datto RMM Jobs - Running jobs on devices
• Datto RMM Sites - Site-level device management
• Datto RMM API Patterns - Authentication and pagination