Skip to main content
POST
Delete a team

Restrictions

Usage

  • At least one of team_id, team_name, or ref_id must be provided.
  • Fails with 400 ReferenceExist if the team is still referenced by schedules, escalation rules, or other resources.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Request identifying a team to delete.

team_id
integer<uint64>

Team ID.

team_name
string

Team name.

ref_id
string

External reference ID.

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
required

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