List User (find where)
Find a list of User records that match the specified criteria.
Tip: All query parameters accept multiple values for array filtering — e.g. ?id=1&id=2 or ?id[]=1&id[]=2. This also works within the where parameter: ?where={"id":[1,2,3]}.
Note: The per-attribute filter parameters and the where parameter are mutually exclusive. If where is supplied, the per-attribute filters are ignored — put all filter criteria inside where instead. limit, skip, sort, and populate are unaffected.
query Parameters
statusFilter by status (1 = active, 0 = inactive)
supervisorID of the associated User record. Default recipient for this user's absence requests. Reserved for expanded use in future approval features.
emailFilter by email
idFilter by record ID
createdAtFilter by creation date (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss.sssZ). This is an exact match filter; for range queries (greater than, less than), use the where parameter instead
updatedAtFilter by last update date (YYYY-MM-DD or YYYY-MM-DDTHH:mm:ss.sssZ). This is an exact match filter; for range queries (greater than, less than), use the where parameter instead
whereA JSON-encoded Waterline criteria for advanced filtering. Only whitelisted criteria are supported: status, supervisor, email, id, createdAt, updatedAt. Sub-attribute modifiers such as startsWith, >=, <=, >, <, and != are supported on any whitelisted criterion. The contains modifier is not supported on this model.
Note: If where is supplied, the per-attribute filter query parameters above are ignored — where is the entire criteria. (limit, skip, sort, and populate are unaffected.) To combine filters, put them all inside where.
e.g. ?where={"startDate":{">=":"2026-06-01","<":"2026-07-01"}}
limitThe maximum number of records to return. Defaults to 10000, capped at 50000.
skipThe number of records to skip (useful for pagination).
sortThe sort order. By default, returned records are sorted by primary key value in ascending order.
e.g. ?sort=lastName%20ASC
List User (find where) › Responses
Responds with a paged list of User records that match the specified criteria
Get User (find one)
Look up the User record with the specified ID.
path Parameters
idThe desired User record's primary key value
Get User (find one) › Responses
Responds with a single User record as a JSON dictionary
Aerion model User
Update User
Partially update an existing User record. Despite using PUT, this endpoint applies PATCH semantics — only the fields included in the request body are modified; omitted fields are left unchanged.
path Parameters
idThe desired User record's primary key value
Update User › Request Body
Aerion model User
Update User › Responses
Responds with the newly updated User record as a JSON dictionary
Aerion model User
Per-month worked / billable / expected hours and overtime
Returns monthly worked hours, billable hours, expected hours (contractual), workload ratio (worked / expected), accrued overtime, and overtime reductions for a user across the year. Callers may read their own data, or anyone's with canAccessUsers or limitedTeamStaffAccess covering the user's team.
path Parameters
userUser ID. Pass 0 to request data for every visible user.
yearCalendar year.
typeRoute pattern variable type
Per-month worked / billable / expected hours and overtime › Responses
Workload
userPresent only when scoped to a single user.
yearGet the currently authenticated user
Returns the User record for the caller, identified by the access token.
Get the currently authenticated user › Responses
Responds with the caller's User record as a JSON dictionary
Aerion model User
Tracking-accuracy scores for users and their teams
Returns submission, validation, and combined day-scores for the requested users (last six months, monthly + all-time) plus the same for the teams they belong to. Scoring weights are configured per account. Callers see scores for users they have access to: canAccessUsers for everyone, otherwise only users in limitedTeamStaffAccess teams.
query Parameters
usersIdsUser IDs to include. Pass repeated usersIds query parameters.
Tracking-accuracy scores for users and their teams › Responses
User and team tracking-accuracy scores