---
title: "Changes to Create a Shield Zone for your PullZone"
method: POST
path: "/shield/shield-zone"
---

# Changes to Create a Shield Zone for your PullZone

`POST /shield/shield-zone`

> Every recorded change to this operation, newest first.

## Timeline

Changed in 2 of 4 revisions.

- **2026-11-12** `6a424e866a61`: 57 warning, 76 info
- **2026-04-18** `18994bc5533c`: 3 info

## Changes

- **2026-11-12** `6a424e866a61`: 57 warning, 76 info
  - removed the request property `shieldZone/blockDatacentre` (media type: application/json)
  - removed the request property `shieldZone/blockDatacentre` (media type: text/json)
  - removed the request property `shieldZone/blockDatacentre` (media type: application/*+json)
  - removed the request property `shieldZone/blockTor` (media type: application/json)
  - removed the request property `shieldZone/blockTor` (media type: text/json)
  - removed the request property `shieldZone/blockTor` (media type: application/*+json)
  - removed the request property `shieldZone/blockVpn` (media type: application/json)
  - removed the request property `shieldZone/blockVpn` (media type: text/json)
  - removed the request property `shieldZone/blockVpn` (media type: application/*+json)
  - removed the request property `shieldZone/dDoSExecutionMode` (media type: application/json)
  - removed the request property `shieldZone/dDoSExecutionMode` (media type: text/json)
  - removed the request property `shieldZone/dDoSExecutionMode` (media type: application/*+json)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `200` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `200` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `200` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `403` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `403` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `403` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `409` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `409` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockDatacentre` from the response with the `409` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `200` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `200` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `200` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `403` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `403` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `403` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `409` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `409` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockTor` from the response with the `409` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `200` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `200` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `200` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `403` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `403` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `403` status (media type: text/json)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `409` status (media type: text/plain)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `409` status (media type: application/json)
  - removed the optional property `data/shieldZone/blockVpn` from the response with the `409` status (media type: text/json)
  - removed the optional property `data/shieldZone/dDoSExecutionMode` from the response with the `200` status (media type: text/plain)
  - …93 more
- **2026-04-18** `18994bc5533c`: 3 info
  - api operation id `Create Shield Zone` was added
  - api tag `Shield Zone` added
  - api tag `ShieldZone` removed

---

[Operation](https://skmtc.dev/bunny/apis/bunny-shield-api/docs/shield/shield-zone/post.md) - [API](https://skmtc.dev/bunny/apis/bunny-shield-api.md) - [Page](https://skmtc.dev/bunny/apis/bunny-shield-api/changes/shield/shield-zone/post)