POST /api/v1/zones

Creates a Network Zone

For an IP Network Zone, you must define either gateways or proxies.
For a Dynamic Network Zone, you must define at least one of the following: asns, locations, or proxyType.
For an Enhanced Dynamic Network Zone, you must define at least one of the following: asns, locations, or ipServiceCategories.

Servers

https://{yourOktaDomain}

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: `"BLOCKLIST"` `"POLICY"`
`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: `true` for system Network Zones `false` for custom Network Zones The Okta org provides the following default system Network Zones: `LegacyIpZone` `BlockedIpZone` `DefaultEnhancedDynamicZone` 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: `"DYNAMIC_V2"` `"DYNAMIC"` `"IP"`
`status`	String	No	Network Zone status Possible values: `"ACTIVE"` `"INACTIVE"`
`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.