Delete Active Account
Permanently deletes your active account — the one your dashboard session is currently in — together with its endpoints, certificates and traffic history. This is the same action exposed in the dashboard under Account Settings → Danger zone ("Delete this account").
You stay signed in. After the account is deleted your session switches to another account you belong to. Because every user must always have at least one account, you cannot delete your only account this way — the request is refused. To close your profile entirely (your login and every account you own), use /user instead.
403 with code: "interactive_session_required". It can only be called from a signed-in dashboard session and requires a step-up re-authentication (your password, plus a 2FA code when MFA is enabled). In practice you trigger it from Account Settings → Danger zone in the dashboard.
Permission required
An interactive session (a signed-in dashboard user), the account owner, and the settings:delete permission on the active account. Non-interactive credentials (API key, OAuth/MCP) are rejected before any check.
Step-up (request body)
Send a JSON body re-confirming the signed-in user. mfa_code is required only when the user has MFA enabled.
401 reauth_required; wrong → 401 invalid_password.401 mfa_required; invalid → 401 invalid_mfa.Before you can delete
The request is blocked with 409 Conflict until every one of these is resolved on the active account:
Resolve these, then retry the request.
Response (200 OK)
true when the account was deleted. Your session then switches to another of your accounts; the response body itself carries only success. Call /account to read the new active context.Errors
code field distinguishes them: reauth_required, invalid_password, mfa_required, invalid_mfa.code: "interactive_session_required" — or: no active account selected, the caller is not the owner, or the caller lacks settings:delete.409 response shape
On a conflict the body is a single human-readable error naming the first unresolved reason. Resolve it and retry; if more than one blocker applies, the next is surfaced on the following attempt: