Operation history

GET 
/vms/:vm_id/operations

Operations and paid orders have different identifiers. Read data.id from a command response as operation_id. queued/running are not completion; succeeded/failed are terminal command results. History may also contain cancelled. result is populated only for successful delete, attach/detach, password reset and reinstall operations; use the status/firewall routes for other current state.

Request rules and errors · Lifecycle · Webhooks

Request

Responses

200

Successful response

401

Missing or invalid key, mismatched ID, or inactive integration

404

Resource not found in this integration

409

Business or state conflict; inspect detail

422

Invalid request fields or unsupported parameters

500

Unexpected server error

503

Service unavailable or result unconfirmed; for a mutation retain its idempotency key