PUT /api/v1/behaviors/{behaviorId}
Replaces a Behavior Detection Rule by behaviorId
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
behaviorId |
String | Yes |
id of the Behavior Detection Rule |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | No | |
created |
String | No | |
name |
String | Yes | |
_link |
Object | No |
Specifies link relations (see Web Linking) available using the JSON Hypertext Application Language specification. This object is used for dynamic discovery of related resources and lifecycle operations. |
type |
String | Yes |
Possible values:
|
status |
String | No |
Possible values:
|
lastUpdated |
String | No |
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.