Modify Client-Side Protections & Compliance settingsCopy Pageput https://{hostname}/appsec/v1/configs/{configId}/versions/{versionNumber}/security-policies/{policyId}/cpcAll products Update Client-Side Protection & Compliance settings for a specific policy.Path ParamsconfigIdint64requiredA unique identifier for each configuration.versionNumberintegerrequiredA unique identifier for each version of a configuration.policyIdstringrequiredA unique identifier for a security policy.Query ParamsaccountSwitchKeystringFor customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.Body ParamsConfiguration settings for Client-Side Protection & Compliance.edgeInjectionobjectrequiredSpecifies the Client-Side Protection & Compliance (CPC) configuration you want to apply, and which pages get monitored by CPC's JavaScript injection to flag suspicious activity. See Client-Side Protection & Compliance for more information.edgeInjection objectedgeTestParametersobjectrequiredUse these query string parameters to unit test an edge server's behavior. Entries here override the sampling percentage, ensuring or disabling JavaScript injection.edgeTestParameters objectinjectionCriteriaobjectrequiredSpecifies the criteria for agent injection.injectionCriteria objectHeadersacceptstringenumDefaults to application/jsonGenerated from available response content typesapplication/jsonapplication/problem+jsonAllowed:application/jsonapplication/problem+jsonResponses 200The response reflects the updated CPC configuration. 400Bad request. Invalid request body or URL parameter input. 403Forbidden. You don't have access to the resource. 404Not found. That resource doesn't exist, or the URL is malformed.Updated 23 days ago