Create a team

POST

/teams

• Local development behind nginx (port 8088 by default)

Requires teams.create. The optional parent_ids array attaches the new team as a child of each listed parent (the DAG case — a team can report to multiple parents). Cycle rejection is enforced by the team_parents trigger.

Authorizations

• cookieAuth
• bearerAuth

Request Body ^required

object

slug

required

string

>= 1 characters <= 80 characters

name

required

string

>= 1 characters <= 200 characters

description

string

<= 500 characters

parent_ids

Optional list of teams to link as parents. Each insert fires the cycle-rejection trigger; the first one that would close a cycle returns 409.

Array<string>

Responses

201

Team created

object

id

required

string format: uuid

slug

required

URL-friendly identifier, unique per origin server. Used in display and (eventually) federation actor URIs.

string

<= 80 characters

Example

aurora-rnd

name

required

string

<= 200 characters

Example

Aurora R&D

description

required

string

<= 500 characters

origin_server_id

Set on rows mirroring a federated team. NULL = locally owned.

string format: uuid

nullable

parents

Direct parent teams (single hop). Empty for root teams. Closure-walked ancestors live behind the listTeams ancestor filter; this field is just the edges out of the current node.

Array<object>

object

parent_id

required

string format: uuid

parent_slug

string

parent_name

string

created_at

required

string format: date-time

updated_at

required

string format: date-time

400

Malformed request

object

error

required

Human-readable error summary

string

Example

the request could not be completed

401

Authentication required, missing, or invalid

object

error

required

Human-readable error summary

string

Example

the request could not be completed

Example

{
  "error": "authentication required: sign in and retry with a valid session or API token"
}

403

Authenticated but missing required capabilities

object

error

required

Human-readable error summary

string

Example

the request could not be completed

404

Resource not found

object

error

required

Human-readable error summary

string

Example

the request could not be completed

409

Conflict (slug taken, would create cycle, etc.)

object

error

required

Human-readable error summary

string

Example

the request could not be completed

500

Unexpected server error

object

error

required

Human-readable error summary

string

Example

the request could not be completed