Create a routing team, then set its members separately

Create a routing team. Team names are unique within a workspace. Members are set separately with PUT /v1/teams/{team_id}/members.

Tenancy: the request is scoped to one workspace, and the credential presented is what selects it. A caller with no membership in that workspace is refused with 404, which is indistinguishable from a workspace that does not exist.

Authorisation: editor, admin or owner. A viewer receives 403 insufficient_role.

Access: Authorization: Bearer carrying either a realm access token or an API key. A key must hold the helpdesk-ops:write scope, and the workspace role of the person who owns it must meet the floor above.

Response Body

curl -X POST "https://example.com/v1/teams" \  -H "Content-Type: application/json" \  -d '{    "name": "Billing"  }'

{}