Skip to main content
GET
JavaScript
Reports the backend’s view of background app-install attempts on this device — one entry per (platform, appId) pair that has an install-app attempt in progress or recently finished.
status reflects the install attempt, not device ground truth. It is running from the moment install-app returns 202, then flips to succeeded or failed once the background download + install finishes. If a running attempt passes its background deadline without a terminal update, this endpoint reports it as failed with errorClass: "timeout". list-apps remains authoritative for what is actually installed — a succeeded entry here is a strong signal, not a guarantee. On some iOS devices, succeeded means the device accepted the install command — the install may still be running on the device, or may yet fail there — so list-apps remains the authoritative check there too.
Unlike most Tools/Apps endpoints, this one is not gated on device readiness — it answers from durable install records, not from the device, so it also works while the device is offline, crashed, or otherwise unreachable. That’s the situation this endpoint exists to surface: an install that fails because the device dropped mid-download has no other way to be observed by a caller. On failure, errorClass narrows down what went wrong from a small closed set:
  • download_failed — fetching the app asset failed
  • adb_install_failed — the download succeeded, but Android refused to install the app (for example a downgrade or a different signing key)
  • timeout — the attempt exceeded its background time budget
  • panic — an unexpected internal error stopped the install
  • failed — anything else
Terminal (succeeded/failed) records are returned for roughly 15 minutes after their last update. A running record that passes its background deadline is projected as failed with errorClass: "timeout" and remains visible for roughly 15 minutes after that deadline. Older records are omitted from this endpoint’s response.
Records are scoped to the tenant that owned the device when the install attempt started: after an ownership transfer (e.g. reassignment or a BYOD re-pair), the new owner cannot see the previous tenant’s install attempts, even while those records are still within their retention window above.

Authorizations

Authorization
string
header
required

Bearer token via Authorization header

Headers

X-Device-Display-ID
integer<int64>
default:0
Required range: x >= 0

Path Parameters

deviceId
string
required

Response

OK

installs
object[] | null
required
$schema
string<uri>
read-only

A URL to the JSON Schema for this object.

Example:

"https://example.com/schemas/ListAppInstallsOutputBody.json"