Delete member
Remove a member from the organization by ID, email, phone, or name.
Restrictions
Usage
- By default (
is_force=false), the system checks whether the member is referenced by other resources (e.g., escalation rules, schedules). If references exist, the API returns error codeReferenceExistwith the reference list indata.refs. Setis_force=trueto skip the reference check and force delete. - Members provisioned via SSO with
sso_user_non_editable=truecannot be deleted through this API. Disable that SSO restriction first. - This operation is recorded in the audit log.
Authorizations
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
Delete member request (provide one of the lookup fields)
Member ID. When several lookup fields are provided, the first non-empty one wins in the order member_id > member_name > email > phone > ref_id
Member name. Only used when member_id is not provided
Email address. Only used when neither member_id nor member_name is provided
Phone number. Only used when member_id, member_name, and email are all absent
Region hint for parsing phone when it has no "+" prefix — an ISO 3166-1 alpha-2 code such as "CN" (the default when omitted). Legacy digit calling codes like "86" are still accepted in this parsing context.
External reference ID. Only used when all other lookup fields are absent
Force delete. Defaults to false, which checks for references from escalation rules, schedules, etc. Set to true to skip the reference check and delete immediately
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.