Clone an FAI configuration version

post

https://{hostname}/appsec/v1/fai-configurations/{faiConfigId}/versions/{version}/clone

This creates a new configuration version based on an existing one. Cloning is how you change a configuration whose version is already active, since an activated version can never be edited again. The clone is a deep copy, carrying over the source version's settings, rules, custom PII types, and application context, so expect that inherited state when you edit it: a custom PII type the clone already carries can't be created again under the same name. The new version becomes the configuration's latest version with an activationStatus of INACTIVE, ready to edit. The Location header of the response gives you the URL of the new version.

Responses

201The response provides the new configuration version, a copy of the source version under a new version number.

400Bad request. The request isn't valid, for example an id that isn't a number, a missing or out-of-range field, a value that isn't allowed, or rule settings that conflict. The detail names the field, the value sent, and what to change.

401Unauthorized.

403Forbidden. You don't have the access this operation needs, or your account isn't entitled to a feature the request uses, such as a rule, the MODIFY action, or languages. The detail says which access or entitlement to ask for.

404Not found. A resource in the URL doesn't exist: the configuration, version, custom PII type, application, access key, or activation. The detail names the missing id and where to find valid ones.

500Internal server error. Something failed on Akamai's side. Try again later. If it keeps happening, contact Akamai support with the instance value.