11.29.0 Changes

What's changed

New inventory fields: last MDM-reported login

Computer and mobile device inventory responses now include the username and timestamp of the last login reported over MDM.

• GET /v1/computers-inventory, /v2/computers-inventory, /v3/computers-inventory (and the /{id} and computers-inventory-detail/{id} variants)

  Added lastLoggedInUsernameMdm and lastLoggedInUsernameMdmTimestamp keys

• GET /v2/mobile-devices/detail, GET /v2/mobile-devices/{id}/paired-devices, and the smart/static group-membership endpoints for /v1 and /v2 mobile device groups

  Added lastLoggedInUsernameMdm and lastLoggedInUsernameMdmTimestamp keys

These are additive — existing integrations keep working and simply see the new keys.

Configuration profile UUIDs in computer inventory

• GET /v1/computers-inventory-detail/{id}, /v2/computers-inventory-detail/{id}, /v3/computers-inventory-detail/{id} (and the computers-inventory/{id} variants)

  Added uuid key to each configuration profile

Platform division identifiers

• GET /v1/auth

  Added divisionId key (per site) and currentDivisionId key (account)

• POST /auth/current

  Added divisionId key (per site)

• GET /v2/mobile-devices/{id}/detail, PATCH /v2/mobile-devices/{id}

  Added divisionId key (site)

divisionId is the Platform division identifier (UUID) for the site.

Mobile device detail can tolerate problem devices

• GET /v2/mobile-devices/detail

  Added the exception-handling query parameter. STRICT (the default) preserves past behavior - a single problem device returns a 500 with details. LENIENT returns a 200 even when some devices have data-processing issues, so one bad record no longer fails the whole request. Default behavior is unchanged.

Jamf Remote Assist returns a clearer status when off

• GET /v1/jamf-remote-assist/session, GET /v1/jamf-remote-assist/session/{id}, GET /v2/jamf-remote-assist/session, GET /v2/jamf-remote-assist/session/{id}, POST /v2/jamf-remote-assist/session/export

  Now return 403 instead of 404 when Jamf Remote Assist isn't available on the instance. The 403 signals the feature isn't enabled, distinct from a missing resource. If your integration treats 404 as "feature unavailable," switch it to check for 403.

Other changes

• GET /v1/auth, POST /auth/current

  The id key for sites is now a string instead of an integer.

• GET /v3/computer-prestages, POST /v3/computer-prestages, GET /v3/computer-prestages/{id}, PUT /v3/computer-prestages/{id}

  Removed the authUrl key.