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

Okta UserFactor API

The UserFactor API from Okta — 7 operation(s) for userfactor.

Okta UserFactor API is one of 28 APIs that Okta publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 4 JSON Schema definitions.

Tagged areas include UserFactor. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, authentication docs, rate-limit docs, a JSON-LD context, and 4 JSON Schemas.

This API exposes 9 operations across 7 paths, and defines 8 schemas. It is described by OpenAPI 3.0.1, at version 2.16.0.

Requests are made against a single base URL, https://your-subdomain.okta.com/.

9 operations 7 paths 8 schemas 1 DELETE5 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
2.16.0
Base URL
https://your-subdomain.okta.com
Authentication
API Key
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Okta UserFactor API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (api_token).

  • api_token — SSWS {API Token}

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 1 DELETE, 5 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

UserFactor 9
GET
/api/v1/users/{userId}/factors
Enumerates all the enrolled factors for the specified user
listFactors 1 param → 200
POST
/api/v1/users/{userId}/factors
Okta Enroll Factor
enrollFactor 5 params body → 200
GET
/api/v1/users/{userId}/factors/catalog
Enumerates all the supported factors that can be enrolled for the specified user
listSupportedFactors 1 param → 200
GET
/api/v1/users/{userId}/factors/questions
Enumerates all available security questions for a user's question factor
listSupportedSecurityQuestions 1 param → 200
GET
/api/v1/users/{userId}/factors/{factorId}
Fetches a factor for the specified user
getFactor 2 params → 200
DELETE
/api/v1/users/{userId}/factors/{factorId}
Unenrolls an existing factor for the specified user, allowing the user to enroll a new factor.
deleteFactor 2 params → 204
POST
/api/v1/users/{userId}/factors/{factorId}/lifecycle/activate
Okta Activate Factor
activateFactor 2 params body → 200
GET
/api/v1/users/{userId}/factors/{factorId}/transactions/{transactionId}
Polls factors verification transaction for status.
getFactorTransactionStatus 3 params → 200
POST
/api/v1/users/{userId}/factors/{factorId}/verify
Okta Verify MFA Factor
verifyFactor 7 params body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are UserFactor (9 properties), VerifyFactorRequest (8 properties), VerifyUserFactorResponse (5 properties), ActivateFactorRequest (5 properties). Each schema is shown below with its type and property counts.

FactorStatus
string
VerifyUserFactorResponse
object
5 properties
FactorType
string
UserFactor
object
9 properties
VerifyFactorRequest
object
8 properties
FactorProvider
string
ActivateFactorRequest
object
5 properties
SecurityQuestion
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

okta-userfactor-api-openapi.yml Raw ↑

Other APIs Okta publishes across the network.

Cross-App Access (XAA)
Okta for AI Agents
Okta Application API
Okta Authenticator API
Okta AuthorizationServer API
Okta Brand API
Okta Domain API
Okta EventHook API
Okta Feature API
Okta Group API
Okta GroupSchema API
Okta IdentityProvider API
Where this information came from

This is an independent, third-party profile of Okta UserFactor 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.