DELETE /v2/tags/{tag_id}/resources

Resources can be untagged by sending a DELETE request to /v2/tags/$TAG_NAME/resources with an array of json objects containing resource_id and resource_type attributes. Currently only untagging of Droplets, Databases, Images, Volumes, and Volume Snapshots is supported. resource_type is expected to be the string droplet, database, image, volume or volume_snapshot. resource_id is expected to be the ID of the resource as a string.

Servers

Path parameters

Name Type Required Description
tag_id String Yes

The name of the tag. Tags may contain letters, numbers, colons, dashes, and underscores. There is a limit of 255 characters per tag.

Request headers

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

Default value: "application/json"

Request body fields

Name Type Required Description
resources[] Array Yes

An array of objects containing resource_id and resource_type attributes.

resources[].resource_type String No

The type of the resource.

Possible values:

  • "droplet"
  • "image"
  • "volume_snapshot"
  • "volume"
resources[].resource_id String No

The identifier of a resource.

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.