---
title: "Perform action on a volume or multiple volumes"
method: PUT
path: "/v1/volumes"
tags: ["Volumes"]
---

# Perform action on a volume or multiple volumes

`PUT /v1/volumes`

## Headers

- `user-agent` string, required
- `cf-connecting-ip` string, required

## Request body

- PerformVolumeActionPublicDto
  - `action` 'attach' | 'detach' | 'delete' | 'rename' | 'resize' | 'restore' | 'clone' | 'cancel' | 'create' | 'export' | 'transfer', required — Action to perform on the volume(s) The `clone` action returns its destination volume ID: `{"id":"..."}`. Send a `cancel` action with that same ID to interrupt a cross-datacenter clone.
  - `id` union, required — Volume ID(s) to perform the action on. Single volume id or an array of volume ids
    - string, uuid
    - string[]
  - `size` number — New volume size in GB. Can't be lower than current size
  - `instance_id` string — Instance ID to attach the volume to, if the action is attach
  - `instance_ids` string[] — Array of instance IDs to attach the volume to, if the action is attach
  - `name` string — New volume name
  - `type` string — Target volume type
  - `is_permanent` boolean — If deleting volume(s), delete them permanently
  - `location_code` string — Target location code if cloning the volume

## Response `202`

---

[API](https://skmtc.net/datacrunch/apis/verda-cloud-public-api.md) · [All operations](https://skmtc.net/datacrunch/apis/verda-cloud-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/datacrunch/verda-cloud-public-api/revisions/0d66c7340876/schema)