How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Frontegg Users API

The Users API from Frontegg — 25 operation(s) for users.

Frontegg Users API is one of 64 APIs that Frontegg publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 26 operations across 25 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 5 base URLs: https://api.frontegg.com/identity, https://api.us.frontegg.com/identity, https://api.ca.frontegg.com/identity, https://api.au.frontegg.com/identity, https://{domain}.frontegg.com/identity.

26 operations 25 paths 28 schemas 1 DELETE6 GET1 PATCH11 POST7 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.frontegg.com/identity
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Frontegg Users API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer).

Paths & Operations 26

Across 25 paths, the API surfaces 26 operations — 1 DELETE, 6 GET, 1 PATCH, 11 POST, 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 26
PUT
/resources/users/temporary/v1/configuration
Set Temporary Users Configuration
TemporaryUsersV1Controller_updateConfiguration body → 200
PUT
/resources/users/v1/{userId}
Update User (global)
UsersControllerV1_updateUserForVendor 1 param body → 200
GET
/resources/vendor-only/users/v1/{userId}
Get User
VendorOnlyUsers_getUserById 1 param → 200
POST
/resources/vendor-only/users/v1/{userId}/mfa/unenroll
Unenroll User From MFA Globally
VendorOnlyUsers_MFAUnenroll 1 param → 200
POST
/resources/vendor-only/users/v1/passwords/verify
Verify User's Password
VendorOnlyUsers_verifyUserPassword body → 200
POST
/resources/vendor-only/users/v1
Create User
VendorOnlyUsers_createUser body → 201
GET
/resources/tenants/users/v1/statuses
Get Users Account (tenant) Statuses
get 2 params → 200
POST
/resources/users/phone-numbers/v1/vendor/{userId}
Create User Phone Number Verified by Default
UserPhoneNumbersControllerV1_createUserPhoneNumberVendor 1 param body → 201
DELETE
/resources/users/phone-numbers/v1/vendor/{userId}/{phoneId}
Delete User Phone Number on an Environment
UserPhoneNumbersControllerV1_deleteUserPhoneNumberVendor 2 params → 200
POST
/resources/users/bulk/v1/invite
Invite Users to an Account (tenant) in Bulk
UsersBulkControllerV1_bulkInviteUsers 1 param body → 202
GET
/resources/users/bulk/v1/status/{id}
Get Status of Bulk Invite Task
UsersBulkControllerV1_getBulkInviteStatus 1 param → 200
PATCH
/resources/vendor-only/users/v1/{userId}/roles/bulk
Bulk Update User Roles Across All Tenants
VendorOnlyUsers_bulkUpdateRolesAcrossAllTenants 1 param body → 200
GET
/resources/vendor-only/users/v1/bulk-roles/status/{taskId}
Get Status of Bulk Roles Update Task
VendorOnlyUsers_getBulkRolesTaskStatus 1 param → 200
GET
/resources/users/v1/email
Get User by Email
UsersControllerV1_getUserByEmail 1 param → 200
GET
/resources/users/v1/{id}
Get User by ID
UsersControllerV1_getUserById 2 params → 200
POST
/resources/users/v1/{userId}/verify
Verify User
UsersControllerV1_verifyUser 1 param → 200
PUT
/resources/users/v1/{userId}/invisible
Make User Invisible
UsersControllerV1_setUserInvisibleMode 1 param body → 200
PUT
/resources/users/v1/{userId}/superuser
Make User Super-user
UsersControllerV1_setUserSuperuserMode 1 param body → 200
PUT
/resources/users/v1/{userId}/tenant
Set User's Account (tenant)
UsersControllerV1_updateUserTenantForVendor 1 param body → 200
POST
/resources/users/v1/{userId}/tenant
Add User to Account (tenant)
UsersControllerV1_addUserToTenantForVendor 1 param body → 201
PUT
/resources/users/v1/{userId}/email
Update User Email
UsersControllerV1_updateUserEmail 1 param body → 200
POST
/resources/users/v1/{userId}/links/generate-activation-token
Generate Activation Token
UsersControllerV1_generateUserActivationLink 1 param → 201
POST
/resources/users/v1/{userId}/links/generate-password-reset-token
Generate Password Reset Token
UsersControllerV1_generateUserPasswordResetLink 1 param → 201
POST
/resources/users/v1/{userId}/unlock
Unlock User
UsersControllerV1_unlockUser 1 param → 200
POST
/resources/users/v1/{userId}/lock
Lock User
UsersControllerV1_lockUser 1 param → 200
PUT
/resources/users/v1/tenants/migrate
Move All Users From One Account (tenant) to Another
UsersControllerV1_moveAllUsersTenants body → 200

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are UserDto (27 properties), CoreUserDto (24 properties), UserBulkInviteRequestDto (13 properties), CreateUserDtoVendorOnly (12 properties). Each schema is shown below with its type and property counts.

CreateUserDtoVendorOnly
object
12 properties 1 required
MigrateUsersFromTenantToTenantRequest
object
2 properties 2 required
AddUserToTenantRequest
object
3 properties 1 required
UserDto
object
27 properties 18 required
UpdateUserSuperuserDto
object
1 property 1 required
CoreUserDto
object
24 properties 16 required
TaskContext
object
GenerateUserActivationLinkResponseDto
object
3 properties 3 required
BulkRolesTaskError
object
4 properties 1 required
UserTenantStatusesResponse
object
2 properties 2 required
UpdateUserTenantWithValidationDto
object
2 properties 1 required
UpdateUserInvisibleDto
object
1 property 1 required
BulkUpdateUserRolesSyncResponseDto
object
4 properties 4 required
UserTenantDto
object
4 properties 2 required
GenerateUserResetPasswordLinkResponseDto
object
3 properties 3 required
TenantStatus
object
2 properties 2 required
BulkRolesTaskStatusResponseDto
object
8 properties 7 required
ValidateUserPasswordResponse
object
UserBulkInviteRequestDto
object
13 properties
PermissionResponse
object
9 properties 9 required
PreVerifyUserPhoneNumberRequestDto
object
1 property 1 required
UpdateUserEmailDto
object
1 property 1 required
ValidateUserPasswordRequest
object
2 properties 2 required
RoleResponse
object
12 properties 12 required
TemporaryUsersConfigurationDto
object
1 property 1 required
BulkUpdateUserRolesRequestDto
object
3 properties
UsersBulkInviteRequestDto
object
1 property 1 required
UpdateVendorUserDto
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

frontegg-users-api-openapi.yml Raw ↑

Other APIs Frontegg publishes across the network.

Frontegg Webhooks
Frontegg Account Invitations API
Frontegg Account Invitations Settings API
Frontegg Account Migration API
Frontegg Account Roles API
Frontegg Account Settings API
Frontegg Accounts API
Frontegg API Access Control API
Frontegg API Access Control Configurations API
Frontegg API Token API
Frontegg API Tokens API
Frontegg Applications Settings API
Where this information came from

This is an independent, third-party profile of Frontegg Users API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.