Hanzo
OpenapiIam

Turns a factor off, so sign-in stops asking for it. — DELETE /v1/iam/mfa

Turns a factor off, so sign-in stops asking for it. Naming no factor turns off ALL of them — the reset path.

DELETE /v1/iam/mfa

Addresshttps://api.hanzo.ai/v1/iam/mfa
MethodDELETE
Operationdelete_iam_mfa
AuthAuthorization: Bearer $HANZO_API_KEY

Turns a factor off, so sign-in stops asking for it. Naming no factor turns off ALL of them — the reset path. People may do this for themselves; doing it for somebody else takes an administrator, which is what makes it the way back in when a phone is lost.

The recovery codes go with the last factor: they are the way past a challenge, so keeping them alive for an account with nothing to challenge would leave a standing credential behind.

Request

DELETE /v1/iam/mfa takes no parameters and no body — the credential is the whole request.

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 has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


IAM API · All Hanzo APIs · Interactive reference

How is this guide?

On this page