---
title: "Get a List of Application Users Across All Applications"
method: GET
path: "/license-manager/application-users"
tags: ["License Manager Public"]
---

# Get a List of Application Users Across All Applications

`GET /license-manager/application-users`

Retrieve a paginated list of users across all applications in your SysAid account. Each user includes a calculated cross-app activity status and the applications they logged in to.

## Query parameters

- `offset` integer
- `limit` integer
- `sortBy` 'email' | 'lastUsageDate'
- `sortDir` 'asc' | 'desc'
- `query` string
- `email` string, email
- `status` 'active' | 'inactive'

## Response `200`

Application user list.

- LicenseManagerCrossAppUsersListResponse
  - `limit` integer — The number of items that are returned per page
  - `offset` integer — The offset used for pagination.
  - `total` integer — The total number of elements across all pages.
  - `data` LicenseManagerCrossAppUser[], required
    - `email` string, required — The email address that appears in the audit logs.
    - `userId` integer, required — The user's unique ID within SysAid
    - `userType` 'agent' | 'end-user', nullable, required — Indicates whether the matched SysAid user is an Agent or an End user. If the value is "null", the user's email doesn't exist in SysAid.
    - `status` 'active' | 'inactive', required — The user's activity status. "active" if the user has logged in to at least one application in the last 30 days. "inactive" otherwise.
    - `lastUsageDate` string, date, nullable, required — The most recent login date across all applications, calculated as the latest lastUsageDate value among all applications the user logged in to. If the value is "null", the user has no recorded login date.
    - `applications` LicenseManagerApplicationReference[], required — The IDs of the applications this user logged into. Use the Applications API to retrieve full application details.
      - `id` string, required — The unique identifier of the application in SysAid (CUID format, 24 characters).

## Other responses

- `400` — The request was invalid or cannot be served
- `401` — Authentication information is missing or invalid
- `403` — The server understood the request but refuses to authorize it
- `500` — An unexpected error occurred on the server

---

[API](https://skmtc.net/sysaid/apis/sysaid-public-api.md) · [All operations](https://skmtc.net/sysaid/apis/sysaid-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sysaid/sysaid-public-api/revisions/38a43a1b2981/schema)