Skip to main content
POST
Delete a team

Restrictions

Usage

  • Provide one of team_id, team_name, or ref_id; when several are sent, team_id wins, then team_name, then ref_id.
  • Besides the permission above, the caller must be a member of the team, its creator, the account owner, or hold the Admin role; otherwise the call returns 403 AccessDenied.
  • Fails with 400 ReferenceExist while the team is still referenced by escalation rules, schedules, channels, notification templates, mapping schemas, service calendars, or the default teams of the SSO configuration; data.refs lists each reference (kind, name, href).
  • Deletion is soft: all members are removed from the team, the team disappears from lists and name/ref_id lookups, its name can be reused, and POST /team/info by team_id still returns it with status deleted.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Request identifying a team to delete.

team_id
integer<uint64>
required

Team ID. At least one of the three lookup fields is required; when several are provided, team_id wins.

team_name
string

Team name. Only used when team_id is not provided.

ref_id
string

External reference ID. Only used when neither team_id nor team_name is provided.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object

Empty object returned on success for operations with no meaningful payload.