PUT /accounts/{account_id}/rulesets/{ruleset_id}

Updates an account ruleset, creating a new version.

Servers

Path parameters

Name Type Required Description
ruleset_id String Yes
account_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
id String Yes

The unique ID of the ruleset.

rules[] Array No

The list of rules in the ruleset.

name String No

The human-readable name of the ruleset.

description String No

An informative description of the ruleset.

last_updated String Yes

The timestamp of when the ruleset was last modified.

version String Yes

The version of the ruleset.

kind String No

The kind of the ruleset.

Possible values:

  • "root"
  • "zone"
  • "managed"
  • "custom"
phase String No

The phase of the ruleset.

Possible values:

  • "magic_transit"
  • "http_custom_errors"
  • "http_ratelimit"
  • "http_response_firewall_managed"
  • "http_request_transform"
  • "http_request_redirect"
  • "ddos_l4"
  • "http_response_compression"
  • "http_response_headers_transform"
  • "http_request_sbfm"
  • "http_log_custom_fields"
  • "magic_transit_ratelimit"
  • "magic_transit_managed"
  • "http_request_cache_settings"
  • "http_request_firewall_custom"
  • "http_request_late_transform"
  • "http_request_dynamic_redirect"
  • "http_request_sanitize"
  • "ddos_l7"
  • "http_config_settings"
  • "http_request_origin"
  • "magic_transit_ids_managed"
  • "http_request_firewall_managed"

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. 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.
  3. Click Test request to test run your request to the API and see the API's response.