API

Deleting your account

Your account's deletion: what a request would get and what stops it, scheduling it with a fresh confirmation, keeping your account, and the link in every notice.

Who can call these. Only your own session in Cactive's apps: ID, or a phone app. API keys, assistants, the command line and other apps get 403 (first_party_only); no MCP tool deletes an account. In practice you delete your account at id.cactive.com.au/delete-account (Account → Profile → Delete Account, or Delete Account in any phone app's account sheet), which calls these routes for you.

Scheduling. POST /v1/me/account/deletion with confirm: "delete" needs a second factor confirmed for deleting your account and a sign-in in the last 10 minutes; the page asks for both. Your account is frozen at once: you're signed out everywhere, apps can't sign in, and your plan stops renewing. It's deleted after the grace period (14 days, or 30 when a password, passkey, two-step sign-in or phone changed in the week before).

Blockers. While you're the last owner of an organization with other members, the only member of one, or the owner of a Mirage server with members, scheduling answers 409 (blocked) with what to do about each.

Keeping your account. Sign in and choose Keep My Account (DELETE /v1/me/account/deletion), or use the link in any email or text about it (POST /v1/account/deletion/cancel, no sign-in needed). After erasure has begun, it's too late (409, too_late).

Every route below, with its parameters, request and response, errors and samples, is in the API reference.

Route	What it does
`POST /v1/account/deletion/cancel`	The link in a deletion notice (no session; ID's cancel page posts it): keeps the account the `token` was sent for. The same answer for any token, spent, unknown or valid; 429 past 10 tries an hour from one network.
`GET /v1/me/account/deletion`	Your account's deletion: the open request (`status`, `eraseAt`, `graceDays`), or, with `status: none`, the grace a request now would get (`graceDays`, and `graceReason: credential_change` when it's longer because a credential changed this week) and the `blockers` to deal with first, each with its `action`. Your own first-party session only (ID, the phone apps), never a key, an assistant or another app.
`POST /v1/me/account/deletion`	Schedules your account's deletion (`confirm: "delete"`, an optional `reason`): it's frozen at once (signed out everywhere, credentials suspended, your plan stops renewing) and erased after the grace, and every address and verified number you have is told, with a link that keeps it. Needs a second factor confirmed for `account_delete` and a sign-in from the last 10 minutes (ID's deletion page gives both), else 403 `step_up`; 403 `first_party_only` for anything but your own session; 409 `blocked` with the `blockers`, or `already_scheduled`; 429 past 3 a month.
`DELETE /v1/me/account/deletion`	Keeps your account: cancels a scheduled deletion ("Keep my account" after signing in). Everything works again; sign in again on your devices. 409 `too_late` once erasure has begun.