Disable 2FA for the caller

POST 
/api/v1/auth/2fa/disable

Disable 2FA for the authenticated user after confirming possession.

Requires a valid TOTP code or a backup code.

Side effects:

• Every server-side trusted-device entry is wiped.

• The __Host-aisafe_trusted_device cookie is cleared on the response so this browser stops sending a stale trust grant.

• 400 if 2FA is not enabled.

• 401 if the verification code is wrong.

• Rate limit: 10 / 15 min / user (auth_mfa tier, 2fa_disable budget — separate from the login budget so a login lockout can't block self-disable; see ).

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.