POST /v2/volumes/{volume_id}/actions

To initiate an action on a block storage volume by Id, send a POST request to ~/v2/volumes/$VOLUME_ID/actions. The body should contain the appropriate attributes for the respective action.

Attach a Block Storage Volume to a Droplet

AttributeDetails
typeThis must be attach
droplet_idSet to the Droplet's ID
regionSet to the slug representing the region where the volume is located

Each volume may only be attached to a single Droplet. However, up to fifteen volumes may be attached to a Droplet at a time. Pre-formatted volumes will be automatically mounted to Ubuntu, Debian, Fedora, Fedora Atomic, and CentOS Droplets created on or after April 26, 2018 when attached. On older Droplets, additional configuration is required.

Remove a Block Storage Volume from a Droplet

AttributeDetails
typeThis must be detach
droplet_idSet to the Droplet's ID
regionSet to the slug representing the region where the volume is located

Resize a Volume

AttributeDetails
typeThis must be resize
size_gigabytesThe new size of the block storage volume in GiB (1024^3)
regionSet to the slug representing the region where the volume is located

Volumes may only be resized upwards. The maximum size for a volume is 16TiB.

Servers

Path parameters

Name Type Required Description
volume_id String Yes

The ID of the block storage volume.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Query parameters

Name Type Required Description
page Integer No

Which 'page' of paginated results to return.

Default value: 1

per_page Integer No

Number of items returned per page

Default value: 20

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.