Hanzo
OpenapiIam

Finishes the enrolment: from here the account's sign-ins ask for this factor.

Finishes the enrolment: from here the account's sign-ins ask for this factor.

POST /v1/iam/mfa/setup/enable

Addresshttps://api.hanzo.ai/v1/iam/mfa/setup/enable
MethodPOST
Operationpost_iam_mfa_setup_enable
AuthAuthorization: Bearer $HANZO_API_KEY

Finishes the enrolment: from here the account's sign-ins ask for this factor. It requires the proof initiate handed out — a passcode from the authenticator, or the code that was sent — and verifies it BEFORE writing anything.

Verifying BEFORE writing is what keeps a client that never completed the proof — a skipped verify step, a QR scanned into the wrong app, a bug — from switching on a factor no code can satisfy. That would lock the account out with no self-service way back: the gate holds the sign-in before minting, so the person could not obtain the bearer that disable requires.

The recovery codes are minted here and returned ONCE, on the first factor the account adds. Answering with them is the way back in when no factor can be produced, so they are the same value the row's digests were made from — by construction, not by a client echoing them back.

Request

The document declares no body for POST /v1/iam/mfa/setup/enable. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_iam_mfa_setup_enable, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo iam mfa setup enable

IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page