List UserAssignment (find where)
Find a list of UserAssignment 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
userFilter by user ID
projectFilter by project ID
isProjectManagerWhen true, grants the assigned user additional permissions to edit this project and its time entries, according to the user's role-level permissions.
isProjectLeadWhen true, this user is designated as the project lead. Grants no extra permissions, but is displayed in the app and can be used for filtering and exporting.
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: user, project, isProjectManager, isProjectLead, 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 100000, 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 UserAssignment (find where) › Responses
Responds with a paged list of UserAssignment records that match the specified criteria
Create UserAssignment
Create a new UserAssignment record.
Create UserAssignment › Request Body
Aerion model UserAssignment
Create UserAssignment › Responses
Responds with a JSON dictionary representing the newly created UserAssignment instance
Aerion model UserAssignment
Get UserAssignment (find one)
Update UserAssignment
Partially update an existing UserAssignment 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 UserAssignment record's primary key value
Update UserAssignment › Request Body
Aerion model UserAssignment
Update UserAssignment › Responses
Responds with the newly updated UserAssignment record as a JSON dictionary
Aerion model UserAssignment