Create Team
POST /teams
Create a team, with its members and channels, in ONE transaction.
Everything in the body lands atomically: a team is never briefly visible with none of its mailboxes attached, and a rejected member id rolls the whole thing back rather than leaving a half-built team.
409 when the name is already taken in this organisation.
Authorizations
Parameters
Header Parameters
Request Body required
Create a team. Mirrors teams.TeamCreateDTO.
Every *_ids list is applied in the SAME transaction as the team row, so
a team is never briefly visible with none of its channels attached.
object
One member in a team’s single-save membership list.
object
Member | manager
Responses
201
Successful Response
object
An open envelope for a single role, team, member or account record.
Open on purpose. The app’s own response models on this surface grow with
the product - RoleResponse gained rep_limits and manages_role_slugs,
TeamResponse gained channel counts and a campaign count - and a pinned
mirror would SILENTLY DROP whatever it had not caught up on. A dropped
permission in a role read is the worst possible kind of stale: it reads as
“they do not have it”.
object
object
Whether there are more pages
Items per page
Current page number (1-indexed)
Total number of items
422
Validation Error