Admin Disable MFA
Turns off one of ANOTHER member’s channels — the route for a member locked out by a lost device, or by a legacy sms enrollment.
{id} is the TARGET, not the administrator.
app, email and sms are all accepted. sms is CLEARING ONLY — the channel is retired and cannot be re-enrolled — and this is the only route that can clear it for somebody else: the whole-account reset DELETE /v1/users/{id}/mfa refuses an administrator’s token, and a member holding only a legacy sms enrollment cannot sign in to obtain their own. Clearing it also unblocks DELETE /v1/users/{id}/phone.
⚠️ This LOWERS someone else’s protection without their participation, and it is the step an attacker who reaches an administrative token would take first.
No confirmation code is taken, by design: an administrator holds neither the member’s authenticator nor their mailbox, so there is no code they could legitimately produce. The administrative MFA resource is what authorizes this route.
On success the response has no body (204).
Failures:
400— the channel name is not one this deployment serves.403— your token does not hold the administrative MFA resource.404— no such user.503 IDE-0066— the identity provider is unavailable (unreachable, too slow to answer, or failing). Nothing about the request was wrong; retry it later.
Authorizations
JWT bearer token issued by the identity provider.
Path Parameters
Target User ID — the member whose channel is being disabled, NOT the administrator.
"00000000-0000-0000-0000-000000000000"
Which channel to disable: app, email, or sms (a legacy enrollment that can be cleared but never re-enrolled).
"app"
Response
No Content

