PUT /api/v1/zones/{zoneId}
Replaces a Network Zone by zoneId. The replaced Network Zone type must be the same as the existing type.
You can replace the usage (POLICY, BLOCKLIST) of a Network Zone by updating the usage attribute.
Servers
- https://{yourOktaDomain}
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
zoneId |
String | Yes |
|
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 Network Zone |
usage |
String | No |
The usage of the Network Zone Possible values:
|
created |
String | No |
Timestamp when the object was created |
name |
String | Yes |
Unique name for this Network Zone |
system |
Boolean | No |
Indicates a system Network Zone:
The Okta org provides the following default system Network Zones:
Admins can modify the name of the default system Network Zone and add up to 5000 gateway or proxy IP entries. |
type |
String | Yes |
The type of Network Zone Possible values:
|
status |
String | No |
Network Zone status Possible values:
|
lastUpdated |
String | No |
Timestamp when the object was last modified |
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.