POST /api/v1/features/{featureId}/{lifecycle}
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.
Servers
- https://{yourOktaDomain}
Path parameters
Name | Type | Required | Description |
---|---|---|---|
lifecycle |
String | Yes |
Whether to Possible values:
|
featureId |
String | Yes |
|
Query parameters
Name | Type | Required | Description |
---|---|---|---|
mode |
String | No |
Indicates if you want to force enable or disable a feature. Supported value is |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.