PUT /api/v1/trustedOrigins/{trustedOriginId}

Replaces a trusted origin

Servers

https://{yourOktaDomain}

Path parameters

Name	Type	Required	Description
`trustedOriginId`	String	Yes	`id` of the trusted origin

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	Unique identifier for the trusted origin
`scopes[]`	Array	No	Array of scope types that this trusted origin is used for
`scopes[].type`	String	No	The scope type. Supported values: When you use `IFRAME_EMBED` as the scope type, leave the `allowedOktaApps` property empty to allow iFrame embedding of only Okta sign-in pages. Include `OKTA_ENDUSER` as a value for the `allowedOktaApps` property to allow iFrame embedding of both Okta sign-in pages and the Okta End-User Dashboard. Valid values: `"CORS"` `"IFRAME_EMBED"` `"REDIRECT"`
`scopes[].allowedOktaApps[]`	Array	No	The allowed Okta apps for the trusted origin scope
`created`	String	No	Timestamp when the trusted origin was created
`name`	String	No	Unique name for the trusted origin
`origin`	String	No	Unique origin URL for the trusted origin. The supported schemes for this attribute are HTTP, HTTPS, FTP, Ionic 2, and Capacitor.
`status`	String	No	Valid values: `"ACTIVE"` `"INACTIVE"`
`lastUpdatedBy`	String	No	The ID of the user who last updated the trusted origin
`createdBy`	String	No	The ID of the user who created the trusted origin
`lastUpdated`	String	No	Timestamp when the trusted origin was last updated

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.