Update VM note
Replace an existing note’s content.
Unlike PUT (which creates the note if missing), PATCH returns 404 when no note exists yet for this scope. Use this when you want to fail loudly if the note isn’t there — i.e. when you intend to edit, not create.
For “create or replace” semantics use PUT /api/v1/vms/{id}/notes/{type}.
For appending without losing existing content use POST /api/v1/vms/{id}/notes/{type}/append.
Authorizations
API key for authentication. Each key is bound to a specific account.
Headers
Project ID. Required for all mutating operations (create, delete, power actions, resize).
Path Parameters
VM ID (UUID)
Note scope. personal is visible only to the writer; account is shared across the account.
personal, account Body
Note text. Pass an empty string to clear the note.