--- title: "Delete a Block Storage Volume by Name" method: DELETE path: "/v2/volumes" tags: ["DigitalOcean-public.v2-new_Block Storage"] --- # Delete a Block Storage Volume by Name `DELETE /v2/volumes` Block storage volumes may also be deleted by name by sending a DELETE request with the volume's **name** and the **region slug** for the region it is located in as query parameters to `/v2/volumes?name=$VOLUME_NAME®ion=nyc1`. No response body will be sent back, but the response code will indicate success. Specifically, the response code will be a 204, which means that the action was successful with no returned body data. ## Query parameters - `name` string - `region` 'ams1' | 'ams2' | 'ams3' | 'blr1' | 'fra1' | 'lon1' | 'nyc1' | 'nyc2' | 'nyc3' | 'sfo1' | 'sfo2' | 'sfo3' | 'sgp1' | 'tor1' | 'syd1' — The slug identifier for the region where the resource will initially be available. ## Response `204` The action was successful and the response body is empty. ## Other responses - `401` — Authentication failed due to invalid credentials. - `404` — The resource was not found. - `429` — The API rate limit has been exceeded. - `500` — There was a server error. - `default` — There was an unexpected error. ## Changes - **2025-10-16** `cb3bf9b21459` — 3 info - the security scope `api:write` was added to the endpoint's security scheme `bearer_auth` - api tag `DigitalOcean-public.v2-new_Block Storage` added - api tag `Block Storage` removed - **2025-07-18** `f8e8c290636c` — 1 info - endpoint added - **2025-07-17** `5fc9af728e82` — 1 breaking - api path removed without deprecation - **2025-07-17** `f8e8c290636c` — 1 info - endpoint added [Change history](https://skmtc.dev/digitalocean/apis/digitalocean-api/changes/v2/volumes/delete.md) --- [API](https://skmtc.dev/digitalocean/apis/digitalocean-api.md) · [All operations](https://skmtc.dev/digitalocean/apis/digitalocean-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/digitalocean/digitalocean-api/revisions/cb3bf9b21459/schema)