Features

The Okta Features API provides operations to manage self-service Early Access (EA) and Beta features in your org.

Note: Important background information for this API is available on the Feature Lifecycle Management page.

List all Features
OAuth 2.0: okta.features.read

Lists all self-service features for your org

Responses
200

Success

403

Forbidden

429

Too Many Requests

get/api/v1/features
Request samples
Response samples
application/json
[]

Retrieve a Feature
OAuth 2.0: okta.features.read

Retrieves a feature by ID

Request
path Parameters
featureId
required
string

id of the feature

Example: R5HjqNn1pEqWGy48E9jg
Responses
200

Success

403

Forbidden

404

Not Found

429

Too Many Requests

get/api/v1/features/{featureId}
Request samples
Response samples
application/json
{}

List all dependencies
OAuth 2.0: okta.features.read

Lists all feature dependencies for a specified feature.

A feature's dependencies are the features that it requires to be enabled in order for itself to be enabled.

Request
path Parameters
featureId
required
string

id of the feature

Example: R5HjqNn1pEqWGy48E9jg
Responses
200

Success

403

Forbidden

404

Not Found

429

Too Many Requests

get/api/v1/features/{featureId}/dependencies
Request samples
Response samples
application/json
[]

List all dependents
OAuth 2.0: okta.features.read

Lists all feature dependents for the specified feature.

A feature's dependents are the features that need to be disabled in order for the feature itself to be disabled.

Request
path Parameters
featureId
required
string

id of the feature

Example: R5HjqNn1pEqWGy48E9jg
Responses
200

Success

403

Forbidden

404

Not Found

429

Too Many Requests

get/api/v1/features/{featureId}/dependents
Request samples
Response samples
application/json
[]

Update a Feature lifecycle
OAuth 2.0: okta.features.manage

Updates a feature's lifecycle status. Use this endpoint to enable or disable a feature for your org.

Use the mode=force parameter to override dependency restrictions for a particular feature. Normally, you can't enable a feature if it has one or more dependencies that aren't enabled.

When you use the mode=force parameter while enabling a feature, Okta first tries to enable any disabled features that this feature may have as dependencies. If you don't pass the mode=force parameter and the feature has dependencies that need to be enabled before the feature is enabled, a 400 error is returned.

When you use the mode=force parameter while disabling a feature, Okta first tries to disable any enabled features that this feature may have as dependents. If you don't pass the mode=force parameter and the feature has dependents that need to be disabled before the feature is disabled, a 400 error is returned.

The following chart shows the different state transitions for a feature.

State transitions of a feature

Request
path Parameters
featureId
required
string

id of the feature

Example: R5HjqNn1pEqWGy48E9jg
lifecycle
required
string (FeatureLifecycle)

Whether to ENABLE or DISABLE the feature

Enum: "DISABLE" "ENABLE"
Example: ENABLE
query Parameters
mode
string

Indicates if you want to force enable or disable a feature. Supported value is force.

Responses
200

Success

403

Forbidden

404

Not Found

429

Too Many Requests

post/api/v1/features/{featureId}/{lifecycle}
Request samples
Response samples
application/json
{}