PUT /accounts/{account_id}/cloudforce-one/rules/{id}
Updates an existing rule.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
The unique identifier for the rule. |
account_id |
String | Yes |
Cloudflare account ID. |
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 |
|---|---|---|---|
commit_message |
String | No |
Human-readable justification for this change. Required for internal-account submissions; optional for customer accounts and automated sync. |
name |
String | No | |
description |
String | No |
Human-readable description of the rule. Auto-extracted from YARA meta if present. |
is_public |
Boolean | No |
Whether this rule is visible to other internal accounts. |
content |
String | No | |
enabled |
Boolean | No |
Whether this rule is active for dice consumers. |
meta[] |
Array | No |
Adds YARA meta entries to the rule's meta block and stores them in rule_meta alongside content metadata. Use valid YARA identifiers for keys; exclude 'name', 'enabled', and 'description'. You may repeat keys. |
meta[].key |
String | Yes | |
meta[].value |
Yes | ||
namespaces[] |
Array | No | |
path |
String | No |
Path change goes through approval workflow. |
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.