Count what deleting this team would unroute, before confirming
The counts a delete confirmation has to state (FR-80): how many current members the team has, and how many non-terminal tickets it routes and would therefore unroute.
/v1/teams/{team_id}/deletion-impactAdmin- Operation id
- team_deletion_impact
- Access
- An editor or a viewer is refused.
/v1/teams/{team_id}/deletion-impactThe counts a delete confirmation has to state (FR-80): how many current
members the team has, and how many non-terminal tickets it routes and would
therefore unroute. Read at the admin floor, the floor of the delete it
describes, so no caller learns from the preview what the action would refuse
to tell them.
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: admin or owner. An editor or 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.
A realm-issued access token, presented as Authorization: Bearer <token>. It acts as the person who signed in, and every operation resolves their workspace role live from the membership record.
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/teams/497f6eca-6276-4993-bfeb-53cbbbba6f08/deletion-impact"{}