PUT /zones/{zone_id}/pagerules/{pagerule_id}
Replaces the configuration of an existing Page Rule. The configuration of the updated Page Rule will exactly match the data passed in the API request.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
pagerule_id |
String | Yes | |
zone_id |
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 |
|---|---|---|---|
priority |
Integer | No |
The priority of the rule, used to define which Page Rule is processed
over another. A higher number indicates a higher priority. For example,
if you have a catch-all Page Rule (rule A: Default value: 1 |
actions[] |
Array | Yes |
The set of actions to perform if the targets of this rule match the request. Actions can redirect to another URL or override settings, but not both. |
targets[] |
Array | Yes |
The rule targets to evaluate on each request. |
status |
String | No |
The status of the Page Rule. Possible values:
Default value: "disabled" |
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.