Skip to content
Users, auth and security...
/
/
Pre-disable SMS MFA

Authentication and Identity Management

Frontegg offers a comprehensive suite of authentication, user management, and security features to streamline identity management and enhance application security. This section provides an overview of all relevant API endpoints, organized into Authentication, Management, and Self-Service categories.

Authentication Endpoints: Enable secure user login, multi-factor authentication (MFA), passwordless options, and social login integrations, allowing for a flexible and robust sign-in experience.

Management Endpoints: Require environment-level authorization and provide full control over SSO (SAML and OpenID Connect) resources, user roles, permissions, and configurations. These endpoints are designed for administrative use, allowing for centralized identity and access management.

Self-Service Endpoints: Accessible with a user token (JWT), these endpoints empower users to manage their SSO connections and other account settings. Users with the necessary permissions can create, update, or delete SSO configurations directly, ensuring they have the tools to manage their access securely and independently.

Each category in this section helps you configure and extend Frontegg’s capabilities, providing the flexibility to manage user identities, authentication protocols, and access controls as per your application’s needs.

Download OpenAPI description
Users, Auth and Security
Single Sign-On
SCIM Provisioning
Entitlements
Entitlements Agent
Accounts (Tenants)
Languages
Servers
EU Region
https://api.frontegg.com/identity/
US Region
https://api.us.frontegg.com/identity/
CA Region
https://api.ca.frontegg.com/identity/
AU Region
https://api.au.frontegg.com/identity/
Frontegg sub-domain for use with user tokens
https://{domain}.frontegg.com/identity/

API token

Operations

General

Operations

MFA

Operations

Disable authenticator app MFA

Request

Disable multi-factor authentication (MFA) enrollment for a logged-in user within a specific account (tenant).

This endpoint removes MFA for a user, typically used in administrative contexts where a backend system or admin manages user security settings.

The request must include the mfaToken, which is the time-based one-time password (TOTP) generated by the user's authenticator app.

Use this endpoint to programmatically disable MFA for a specific user within an account (tenant).

Security
bearer
Path
deviceIdstringrequired
Headers
frontegg-user-idstringrequired

The user ID identifier

Bodyapplication/jsonrequired
tokenstring
curl -i -X POST \
  'https://api.frontegg.com/identity/resources/users/v1/mfa/authenticator/{deviceId}/disable/verify' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'frontegg-user-id: string' \
  -d '{
    "token": "string"
  }'

Responses

Pre-disable SMS MFA

Request

Initiate the process of disabling SMS-based multi-factor authentication (MFA) for a specific device.

Provide the target deviceId in the request path to mark the SMS MFA device for pre-disablement. This action prepares the device for subsequent steps required to complete the removal.

Use this route as part of the MFA management flow for disabling SMS-based MFA on a per-device basis.

Security
bearer
Path
deviceIdstringrequired
Headers
frontegg-user-idstringrequired

The user ID identifier

frontegg-tenant-idstringrequired

The account (tenant) ID identifier

Bodyapplication/jsonrequired
object(RequestDisableMFARequest)
curl -i -X POST \
  'https://api.frontegg.com/identity/resources/users/v1/mfa/sms/{deviceId}/disable' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'frontegg-tenant-id: string' \
  -H 'frontegg-user-id: string' \
  -d '{}'

Responses

Bodyapplication/json
object(RequestDisableMFASMSResponse)
Response
application/json
{}

Disable SMS MFA

Request

Complete the process of disabling SMS-based multi-factor authentication (MFA) for a specific device.

This step finalizes MFA deactivation for the given deviceId after a prior pre-disable action.

The request must include:

  • otcToken: The one-time challenge token obtained during the pre-disable step.
  • code: The SMS verification code received by the user.

Use this endpoint as the second step in the SMS MFA removal flow to verify the user's identity and confirm the disable action.

Security
bearer
Path
deviceIdstringrequired
Headers
frontegg-user-idstringrequired

The user ID identifier

Bodyapplication/jsonrequired
otcTokenstringrequired
codestringrequired
curl -i -X POST \
  'https://api.frontegg.com/identity/resources/users/v1/mfa/sms/{deviceId}/disable/verify' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -H 'frontegg-user-id: string' \
  -d '{
    "otcToken": "string",
    "code": "string"
  }'

Responses

Passwordless

Operations

SMS

Operations

Account invitations settings

Operations

Core settings

Operations

Custom social OAuth provider

Operations

Data migration

Operations

Delegation

Operations

Email configuration

Operations

Email templates

Operations

M2M tokens

Operations

MFA configuration

Operations

Permissions categories

Operations

Permissions

Operations

Roles

Operations

SMS configuration

Operations

SMS templates

Operations

Sessions configuration

Operations

User pools

Operations

Users

Operations

Account invitations

Operations

Account roles

Operations

API tokens

Operations

Domain restrictions

Operations

IP restrictions

Operations

Lockout policy

Operations

MFA settings

Operations

Password settings

Operations

Personal tokens

Operations

Sessions management

Operations

User groups

Operations

User management

Operations

User sessions

Operations

Users-applications management

Operations