A Change may allow for, or require updates to be made under certain conditions. The type of updates allowed is internal to the system, and is determined by the state of the change as well as the specific enrollment type. Clients have to inspect the allowedInput[].type returned by Get change status operation to determine actions and headers supported, then use the Accept and Content-Type headers for the respective allowedInput value to inspect or perform updates to the Change. The following table presents an overview of the different types and corresponding headers. The table helps you identify which headers you can use when performing the Get a change and Update a change operations.

allowedInput[].‚ÄčtypeAPI typeDescriptionContent-Type headerAccept header
Change-Management
change-management-infoinfo / GETChange Management information provides acknowledgement status, and may include warnings about potential conflicts that may occur if you proceed with acknowledgement.N/Aapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčchange-management-info.‚Äčv4+json
change-management-infoinfo / GETThe Deployment currently deployed to the staging network. Acknowledging change-management continues deploying this configuration to the production network.N/Aapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčdeployment.‚Äčv1+json
change-management-ackupdate / POSTAcknowledge Change Management is required to proceed deploying the certificate to the production network.application/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčacknowledgement-with-hash.‚Äčv1+jsonapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčchange-id.‚Äčv1+json
Let's Encrypt
lets-encrypt-challengesinfo/ GETGet Let's Encrypt DvChallenges for a given change.N/Aapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčdv-challenges.‚Äčv2+json
lets-encrypt-challenges-completedupdate / POSTSubmit an acknowledgement after you place the HTTP or DNS tokens to inform CPS that Let's Encrypt challenges have been made available and are ready for validation. You can also wait for CPS to check for the tokens, which it does on a regular schedule.application/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčacknowledgement.‚Äčv1+jsonapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčchange-id.‚Äčv1+json
Post-Verification
post-verification-warningsinfo / GETPost-verification Warnings generated for a given change. Produced after CPS retrieves a certificate from a CA or when a client uploads a certificate. You must acknowledge post-verification warnings for the change to continue processing.N/Aapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčwarnings.‚Äčv1+json
post-verification-warnings-ackupdate / POSTYou must acknowledge post-verification warnings by submitting an acknowledgement.application/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčacknowledgement.‚Äčv1+jsonapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčchange-id.‚Äčv1+json
Pre-Verification
pre-verification-warningsinfo / GETPre-verification Warnings can generate for a given change. CPS produces these after it retrieves a certificate from a CA or after a client uploads the certificate. Post-verification Warnings must be acknowledged for the change to continue processing.N/Aapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčwarnings.‚Äčv1+json
pre-verification-warnings-ackupdate / POSTYou must acknowledge pre-Verification warnings by submitting an acknowledgement.application/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčacknowledgement.‚Äčv1+jsonapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčchange-id.‚Äčv1+json
Third-Party
third-party-csrinfo / GETGet Certificate Signing Request (CSR) for a Third-Party certificate.N/Aapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčcsr.‚Äčv1+json
third-party-cert-and-trust-chainupdate / POSTUpload Third Party Certificate and Trust Chain.application/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčcertificate-and-trust-chain.‚Äčv1+jsonapplication/‚Äčvnd.‚Äčakamai.‚Äčcps.‚Äčchange-id.‚Äčv1+json