---
title: "Mark MFA as enabled"
method: POST
path: "/api/experience/profile/mfa/mfa-enabled"
tags: ["Experience"]
---

# Mark MFA as enabled

`POST /api/experience/profile/mfa/mfa-enabled`

Mark the user's MFA as enabled for the current interaction and persist in DB user configs upon successful submission.

## Response `204`

The MFA has been successfully marked as enabled. This is typically useful for optional MFA scenarios as the client can prompt an MFA enrollment flow if the user has not enabled MFA yet, for added security.

## Other responses

- `400` — Not supported for the current interaction event. The MFA profile API can only be used in the `SignIn` or `Register` interaction.
- `403` — MFA verification is required but has not been completed. The user must verify the existing MFA before updating MFA settings.
- `404` — The user has not been identified yet. The `mfa-enabled` configuration must be associated with an identified user.

---

[API](https://skmtc.net/logto/apis/logto-api-references.md) · [All operations](https://skmtc.net/logto/apis/logto-api-references/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/logto/logto-api-references/revisions/a163dc77d842/schema)