This workflow shows you how to make changes to a configuration version including adding new hostnames, and then activating the changes you've made.
- 
Run List configurations and select a
configId. - 
Run List configuration versions and select a
versionNumber. - 
You cannot edit the configuration version if it's ACTIVE on staging or production servers. To create a new version, run Clone a configuration version.
 - 
Add hostnames to the response object.
 - 
Make a PUT request to
/appsec/v1/configs/{configId}/versions/{versionNumber}/selected-hostnames. - 
Run List security policies and select a
policyId. - 
Run Create a match target and select the new match target's
targetIdfrom the response. - 
Run Get a match target.
 - 
Modify the MatchTarget object.
 - 
Make a PUT request to
/appsec/v1/configs/{configId}/versions/{versionNumber}/match-targets/{targetId}. - 
Run List match targets.
 - 
Craft a MatchTargetOrder object using the
targetIds. - 
Make a PUT request to
/appsec/v1/configs/{configId}/versions/{versionNumber}/match-targets/sequence. - 
Create an Activation object.
 - 
Make a POST request to
/appsec/v1/activationsto activate the configuration version. - 
Run Get activation status to check the activation status.
 
