List TeamAssignment (find where)
Find a list of TeamAssignment 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
teamID of the associated Team record. Cannot be changed after creation.
userFilter by user ID
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: team, user, 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 TeamAssignment (find where) › Responses
Responds with a paged list of TeamAssignment records that match the specified criteria
Create TeamAssignment
Create a new TeamAssignment record.
Only one assignment can exist per (user, team) pair — a user cannot be both guest and non-guest on the same team. A user can also have at most one non-guest assignment overall; to move a user to a different primary team, delete their existing non-guest assignment first, then create the new one.
Create TeamAssignment › Request Body
Aerion model TeamAssignment
Create TeamAssignment › Responses
Responds with a JSON dictionary representing the newly created TeamAssignment instance
Aerion model TeamAssignment
Get TeamAssignment (find one)
Update TeamAssignment
Partially update an existing TeamAssignment record. Despite using PUT, this endpoint applies PATCH semantics — only the fields included in the request body are modified; omitted fields are left unchanged.
user and team cannot be changed after creation. To move a user to a different team, delete this assignment and create a new one.
path Parameters
idThe desired TeamAssignment record's primary key value
Update TeamAssignment › Request Body
Aerion model TeamAssignment
Update TeamAssignment › Responses
Responds with the newly updated TeamAssignment record as a JSON dictionary
Aerion model TeamAssignment