{
  "opencollection": "1.0.0",
  "info": {
    "name": "Akamai: Application Security Activation history Attack payload logs API",
    "version": "v1"
  },
  "items": [
    {
      "info": {
        "name": "Attack payload logs",
        "type": "folder"
      },
      "items": [
        {
          "info": {
            "name": "Akamai API Security Get the Attack Payload Log Settings for a Configuration",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://{hostname}/appsec/v1/configs/:configId/versions/:versionNumber/advanced-settings/logging/attack-payload",
            "params": [
              {
                "name": "configId",
                "value": "{{configId}}",
                "type": "path",
                "description": "A unique identifier for each configuration."
              },
              {
                "name": "versionNumber",
                "value": "{{versionNumber}}",
                "type": "path",
                "description": "A unique identifier for each version of a configuration."
              },
              {
                "name": "accountSwitchKey",
                "value": "{{accountSwitchKey}}",
                "type": "query",
                "description": "For customers who manage more than one account, this [runs the operation from another account](https://techdocs.akamai.com/developer/docs/manage-many-accounts-with-one-api-client). The Identity and Access Management API provides a [list of available account switch keys](https://techdocs.akamai.com/iam-api/reference/get-client-account-switch-keys)."
              }
            ]
          },
          "docs": "Lists attack payload log settings for a configuration. When set to `NONE`, the request body and response body show as redacted in the log. For example, `JSON_PAIRS:redacted`. Attack payload logging is on by default, and in most cases you should leave it enabled. This operation applies at the configuration level, and therefore applies to all policies within a configuration. If you want to view these settings for a specific policy, run [Get attack payload logging settings for a policy](https://tec"
        },
        {
          "info": {
            "name": "Akamai API Security Modify Attack Payload Log Settings for a Configuration",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://{hostname}/appsec/v1/configs/:configId/versions/:versionNumber/advanced-settings/logging/attack-payload",
            "params": [
              {
                "name": "configId",
                "value": "{{configId}}",
                "type": "path",
                "description": "A unique identifier for each configuration."
              },
              {
                "name": "versionNumber",
                "value": "{{versionNumber}}",
                "type": "path",
                "description": "A unique identifier for each version of a configuration."
              },
              {
                "name": "accountSwitchKey",
                "value": "{{accountSwitchKey}}",
                "type": "query",
                "description": "For customers who manage more than one account, this [runs the operation from another account](https://techdocs.akamai.com/developer/docs/manage-many-accounts-with-one-api-client). The Identity and Access Management API provides a [list of available account switch keys](https://techdocs.akamai.com/iam-api/reference/get-client-account-switch-keys)."
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Enable, disable, or update attack payload log settings for a configuration. When set to `NONE`, the request body and response body show as redacted in the log. For example, `JSON_PAIRS:redacted`. When set to `RESPONSE_BODY` or `REQUEST_BODY` the log shows only the string flagged as a possible attack, and not the entire request or response body. This operation applies at the configuration level, and therefore applies to all policies within a configuration. If you want to override these settings f"
        },
        {
          "info": {
            "name": "Akamai API Security Get Attack Payload Logging Settings for a Policy",
            "type": "http"
          },
          "http": {
            "method": "GET",
            "url": "https://{hostname}/appsec/v1/configs/:configId/versions/:versionNumber/security-policies/:policyId/advanced-settings/logging/attack-payload",
            "params": [
              {
                "name": "configId",
                "value": "{{configId}}",
                "type": "path",
                "description": "A unique identifier for each configuration."
              },
              {
                "name": "versionNumber",
                "value": "{{versionNumber}}",
                "type": "path",
                "description": "A unique identifier for each version of a configuration."
              },
              {
                "name": "policyId",
                "value": "{{policyId}}",
                "type": "path",
                "description": "A unique identifier for a security policy."
              },
              {
                "name": "accountSwitchKey",
                "value": "{{accountSwitchKey}}",
                "type": "query",
                "description": "For customers who manage more than one account, this [runs the operation from another account](https://techdocs.akamai.com/developer/docs/manage-many-accounts-with-one-api-client). The Identity and Access Management API provides a [list of available account switch keys](https://techdocs.akamai.com/iam-api/reference/get-client-account-switch-keys)."
              }
            ]
          },
          "docs": "List a security policy's settings for attack payload logging. Attack payload logging is on by default, and in most cases you should leave it enabled. When set to `NONE`, the request body and response body appear as `redacted` in the log. For example, `JSON_PAIRS:redacted`. This operation applies at the security policy level, and overrides the attack payload logging settings at the configuration level on a per-policy basis. _Products:_ All."
        },
        {
          "info": {
            "name": "Akamai API Security Modify Attack Payload Logging Settings for a Policy",
            "type": "http"
          },
          "http": {
            "method": "PUT",
            "url": "https://{hostname}/appsec/v1/configs/:configId/versions/:versionNumber/security-policies/:policyId/advanced-settings/logging/attack-payload",
            "params": [
              {
                "name": "configId",
                "value": "{{configId}}",
                "type": "path",
                "description": "A unique identifier for each configuration."
              },
              {
                "name": "versionNumber",
                "value": "{{versionNumber}}",
                "type": "path",
                "description": "A unique identifier for each version of a configuration."
              },
              {
                "name": "policyId",
                "value": "{{policyId}}",
                "type": "path",
                "description": "A unique identifier for a security policy."
              },
              {
                "name": "accountSwitchKey",
                "value": "{{accountSwitchKey}}",
                "type": "query",
                "description": "For customers who manage more than one account, this [runs the operation from another account](https://techdocs.akamai.com/developer/docs/manage-many-accounts-with-one-api-client). The Identity and Access Management API provides a [list of available account switch keys](https://techdocs.akamai.com/iam-api/reference/get-client-account-switch-keys)."
              }
            ],
            "body": {
              "type": "json",
              "data": "{}"
            }
          },
          "docs": "Update attack payload logging settings for a specific policy. This operation applies at the security policy level, and overrides the attack payload logging settings at the configuration level on a per-policy basis. When set to `NONE`, the request body and response body appear as `redacted` in the log. For example, `JSON_PAIRS:redacted`. _Products:_ All."
        }
      ]
    }
  ],
  "bundled": true
}