Start 2FA (TOTP) enrolment

POST 
/api/v1/auth/2fa/enable

Start 2FA enrolment and return a QR code and manual entry secret.

The user must confirm enrolment with POST /2fa/verify before 2FA is fully enabled; until then the generated TOTP secret is stored but totp_enabled remains false.

• 400 if 2FA is already enabled for the caller.

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.