You can manage network zones programmatically using the Settings API with the builtin:networkzones.zones schema. This page covers the network-zone-specific details. For general Settings API behavior—pagination, filtering, and error responses—see the Settings API reference.
All requests require an API token. To learn how to obtain and use it, see Authentication.
The required token permission depends on the operation:
settings.read)—required for listing all network zones and retrieving a single network zonesettings.write)—required for creating, updating, and deleting network zonesAll operations use the /api/v2/settings/objects endpoint. Prepend the base URL for your deployment to the path shown in the table below:
SaaS https://{your-environment-id}.live.dynatrace.com
| Operation | Method | Path | Required scope |
|---|---|---|---|
|
|
| |
|
|
| |
|
|
| |
|
|
| |
|
|
|
The create and update operations accept a value object in the request body. Its properties are described below.
| Field | Type | Required | Description |
|---|---|---|---|
| string | Yes | Unique identifier of the network zone. Alphanumeric characters, hyphens ( |
| string | No | Human-readable description of the network zone. |
| array of strings | Yes | List of alternative network zone IDs to use when no ActiveGate in this zone is available. Can be empty. See Alternative network zone. |
| string | Yes | Routing behavior when no ActiveGate is available in this zone or its alternatives. See Fallback mode for a description of each option. Valid values: |
GET /api/v2/settings/objects/{object-id}
Response; not all properties are shown in this example:
{"objectId": "<objectId>","created": 1782827712752,"modified": 1782887796575,"scope": "environment","schemaId": "builtin:networkzones.zones","value": {"id": "my-network-zone","alternativeZones": [],"fallbackMode": "ANY_ACTIVE_GATE"}}
POST /api/v2/settings/objects[{"schemaId": "builtin:networkzones.zones","scope": "environment","value": {"id": "my-network-zone","description": "My new network zone","alternativeZones": [],"fallbackMode": "ANY_ACTIVE_GATE"}}]
Response; returns the status and object ID of the created network zone:
[{"code": 200,"objectId": "<objectId>"}]
The request body must include all fields; this is a full replacement, not a partial update. The id field must be present but cannot be changed.
PUT /api/v2/settings/objects/{object-id}{"value": {"id": "my-network-zone","description": "Updated description","alternativeZones": [],"fallbackMode": "ANY_ACTIVE_GATE"}}
Response:
{"code": 200,"objectId": "<objectId>"}
DELETE /api/v2/settings/objects/{object-id}
A successful deletion returns 204 No Content with no response body.