List devices that you have access to.

Note: This checks for username and reseller ID based devices. That is, administrative API keys will not return every DNA in the database.

If you have no DNAs, an empty array is returned.

Example Response

 [
    "0060FF3A4477",
    "0060FDB0221C",
 ]

Get a full-fledged fleet overview for devices you have access to, instead of just listing MAC addresses.

Note: This checks for username and reseller ID based devices. That is, administrative API keys will not return every DNA in the database.

If you have no DNAs, an empty array is returned.

See GET /dna-api/v1/devices/{mac}/ for sample output.

Example Response

{
     "mac": "0082E065F560",
     "hostname": "DattoDNA",
     "lastCheckin": 1507298576,
     "version": "1.1.1.77",
     "uptime": 68421,
     "connectedDevices": 1,
     "openMeshDevices": [
         {
             "leased": "1510731430",
             "id": "ac8674978ea0",
             "ip": "192.168.17.86",
             "hostname": "*",
             "forWindowsHost": "01:ac:86:74:97:8e:a0"
         }
     ],
     "failover": false,
     "downtime": [
         {
             "start": 1507487717,
             "stop": 1507487900
         },
         {
             "start": 1507487717
         }
     ]
 }

Notes:

• Uptime refers to the unix uptime of the device, i.e., how long since it was last rebooted.
• Downtime is reported on a 24 hour window. If no "stop" key exists, then the device is currently offline
• In all cases, we report on the last known status of the device.

View top applications used by clients connected to a DNA.

Currently, you can choose between receiving data accumulated over the last week, or over the last year.

By default, the top 10 applications by bandwidth are displayed. You can change this via the "limit" paramter.

Note that the totalBytes response field shows the sum of all applications, not just the ones displayed.

Example Response

 {
     "apps": [
         {
             "name": "skype",
             "type": 7,
             "bytes": 69121
         }
         {
             "name": "youtube",
             "type": 10,
             "bytes": 14553
         }
     ],
     "totalBytes": 127528
 }

Return the client overview over a specified time period.

The aggregation period is configurable via the window parameter, and defaults to one day. This is a rolling window, where the upper bound is the time of the request.

If no data is available, an empty array is returned.

Example Response

{
     "currentConnectedClients": [
         {
             "id":"vlan2",
             "devices":[
                 {
                     "leased": "1506401611",
                     "id": "00012e58c931",
                     "ip": "192.168.100.189",
                     "hostname": "belair",
                     "forWindowsHost": "*"
                 },
             ]
         },
         {
             "id":"vpn0",
             "devices":[]
         }
     ],
     "openMeshClients": 25,
     "distinctClients": 43,
     "totalUpload": "45230159",
     "totalDownload": "298123598"
 }

Get the bandwidth usage of clients connected to a DNA, reported in bytes.

Although not all clients may be shown, the reported usagePercent accounts for all bandwidth captured. (As such, the combined percentages will be less than 100% should any clients be truncated.)

The aggregation period is configurable via the window parameter, and defaults to three months. This is a rolling window, where the upper bound is the time of the request.

If a client was leased multiple IP addresses throughout the aggregation period, the most recent IP will be used.

If no data is available, an empty array is returned.

Example Response

[
    {
        "mac": "33A4C487233D",
        "ip": "172.20.95.116"
        "usage": 180792,
        "usagePercent": 11.39
    },
    {
        "mac": "A17BD9B52FDE",
        "ip": "192.168.37.214"
        "usage": 120936,
        "usagePercent": 7.62
    },
    ...
    ...
]

Get the bandwidth usage a DNA's WANs, reported in bytes.

The time period is configurable via the window parameter, and defaults to one day. This is a rolling window, where the upper bound is the time of the request.

The granularity of the data correlates to the time period requested:

  > If the window is equal to one hour, you will receive data aggregated by the minute.

  > If the window is greater than one hour, you will receive data aggregated by the hour.

  > If the window is greater than one week, you will receive data aggregated by the day.

In general, data will not be spaced perfectly evenly. Requesting one week of data will usually return more than 7 data points, as we will send the results for this day so far, as well as a corresponding portion of the 7th day prior.

We interpret calendar days, weeks, etc. based on GMT (Greenwich Mean Time), which currently corresponds to UTC.

It is also possible, although highly unlikely, that datapoints are missing. Please contact tech support if you feel that is the case and we will investigate.

Finally, the granularity is determined by the actual size of the window, and not the format used to request it. For example, requesting '5000h' (five thousand hours) of data will still result in daily chunks.

If no data is available, an empty array is returned.

Example Response

{
    "vlan1": {
        "1488745067": {
            "up": 1867,
            "down": 65142
        },
        "1489004267": {
            "up": 1484,
            "down": 11461
        },
    ...
    ...
]

Example Response

{
     "hostname": "DNA",
     "model": "DNA-VZ4",
     "lastSeen": 1507298576,
     "version": "1.1.1.77",
     "uptime": 48903893,
     "networks": [],
     "subnets": [],
     "failover": [],
}

Redirects the user to the Datto SSO login page. Once the user authenticates there, they will be returned to this application.

Currently, this is the only URL accessible without any form of credentials.

Reports the currently logged in user, as a keyed JSON object.

Example Response

{
    "username": "Waldo",
}

This call provides the caller with the network overview information for any given reseller's list of devices.

Please see GET /dna-api/v1/devices/{mac} for an example of what a DNA's overview looks like.

To access this endpoint, you must use an API key scoped to the requested reseller (or be an admin).

Get devices available to an SSO user as a JSON array.

We first send the username to portal's System API, to get a list of DNA's the user is allowed to view. We then search our database for those MAC addresses, and return the resulting set. (Hopefully, the two sets are equal!)

MAC addresses are capitalized, with no delimiters.

If no devices are found, an empty array is returned.

Example Response

[
    "0060FF3A4400",
    "0060F883BCA6"
]