Stage Pending
If vSphere APIs begin with /rest (vs /api), any maps are consumed/returned instead as arrays of objects, each containing a key and a value property field.
Starts staging the appliance update. The updates are searched for in the following order: staged, CDROM, URL
Request
URLURL
https://{api_host}/rest/appliance/update/pending/{version}?action=stage
Parameters
Parameters
string
version
Required
Update version
The parameter must be an identifier for the resource type: com.vmware.appliance.update.pending.
Header Parameters
Header Parameters
string
vmware-api-session-id
Required
Required session ID, obtained by first calling Create Session API
Example: b00db39f948d13ea1e59b4d6fce56389
cURL Command
curl -X POST -H "vmware-api-session-id: b00db39f948d13ea1e59b4d6fce56389" https://{api_host}/rest/appliance/update/pending/{version}?action=stage
Errors
401
com.vmware.vapi.std.errors.unauthenticated : session is not authenticated | com.vmware.vapi.std.errors.unauthorized : session is not authorized to perform this operation
404
com.vmware.vapi.std.errors.error : Generic error | com.vmware.vapi.std.errors.not_found : the update is not found
409
com.vmware.vapi.std.errors.already_in_desired_state : if the update of this version is already installed | com.vmware.vapi.std.errors.already_exists : the update is already staged | com.vmware.vapi.std.errors.not_allowed_in_current_state : if appliance update state prevents staging
On This Page
Pending Operations
get
get
post
post
post
post
