PUT /api/v1/inlineHooks/{inlineHookId}

Replaces an inline hook by inlineHookId

Servers

https://{yourOktaDomain}

Path parameters

Name	Type	Required	Description
`inlineHookId`	String	Yes	`id` of the Inline Hook

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
`_links`	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.
`channel`	Object	No
`channel.version`	String	No
`channel.type`	String	No	Possible values: `"OAUTH"` `"HTTP"`
`created`	String	No
`name`	String	No
`version`	String	No
`metadata`	Object	No	Specific properties for the inline hook configuration, for example, `optOutServiceProtectionRateLimit` to opt-out of Telephony Service Protection Rate Limits when using the Telephony inline hook.
`type`	String	No	Possible values: `"com.okta.import.transform"` `"com.okta.user.pre-registration"` `"com.okta.telephony.provider"` `"com.okta.oauth2.tokens.transform"` `"com.okta.saml.tokens.transform"` `"com.okta.user.credential.password.import"`
`status`	String	No	Possible values: `"ACTIVE"` `"INACTIVE"`
`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.