POST Codesign/UpdateApplicationCollection
                                                        Updates the set signing tools in an Application collection.
Requirements
- Permissions: The caller must be a Code Signing Administrator or application administrator. 
- Token scope: Codesign:Manage
Headers
- 
                                                                Content type: Content-Type:application/json. 
- Token: The bearer access token that you received. For example, Authorization:Bearer 4MyGeneratedBearerTknz==. For more information, see Passing a bearer token in your API calls.
Parameters
| Name | Description | 
|---|---|
| ApplicationCollection | The entire ApplicationCollection object. To get this value, call POST Codesign/EnumerateApplicationCollections. | 
Returns
| Name | Description | 
|---|---|
| HTTP 200 | For valid requests, this call returns a HTTP 200 message and the following data in the message body: 
 | 
| HTTP 400 | For invalid requests, this call returns HTTP 400 Bad Request and the following data in the message body: 
 | 
Example: Add Jarsigner to an application collection
Request
POST https://codesign.venafi.example/vedsdk/Codesign/UpdateApplicationCollection
Authorization:Bearer 4MyGeneratedBearerTknz==
{
   "ApplicationCollection":{
      "ApplicationDNs":{
         "Items":[
            "\\VED\\Code Signing\\Signing Applications\\Jarsigner - 11",
            "\\VED\\Code Signing\\Signing Applications\\Powershell - x64",
            "\\VED\\Code Signing\\Signing Applications\\Powershell - x86"
         ]
      },
      "Dn":"\\VED\\Code Signing\\Signing Applications\\MySigningToolset",
      "Guid":"{e17b907c-9865-4402-ba1f-c79df84548ee}",
      "Id":409
   }
}
        
                                                        Response
HTTP/1.1 200 OK
{
   "Result": 1,
   "Success": true
}