Teams
Teams group users for escalation targets and access control. A user may belong to multiple teams.
Endpoints
Section titled “Endpoints”| Method | Path | Description | Scope |
|---|---|---|---|
GET | /api/v1/teams | List teams. | teams |
POST | /api/v1/teams | Create. | teams |
GET | /api/v1/teams/{id} | Read. | teams |
PATCH | /api/v1/teams/{id} | Update metadata. | teams |
DELETE | /api/v1/teams/{id} | Delete. Fails if referenced by a policy or service. | teams |
POST | /api/v1/teams/{id}/members | Add member. | teams |
PATCH | /api/v1/teams/{id}/members/{userID} | Update member role. | teams |
DELETE | /api/v1/teams/{id}/members/{userID} | Remove member. | teams |
Create a team
Section titled “Create a team”{ "name": "Platform", "description": "Platform engineering team.", "default_notify_channel_id": "01HXCHAN..."}Add a member
Section titled “Add a member”POST /api/v1/teams/{id}/members{ "user_id": "usr_alice", "role": "lead"}role | Meaning |
|---|---|
member | Receives team-targeted notifications. |
lead | Member + allowed to edit team metadata and roster. |
Changing a member’s role: PATCH /teams/{id}/members/{userID} with { "role": "lead" }.